DTD definition in DCR format Data Record

cmurphy1984

We recently converted from TPL PTs to XSL PTs and have run into a problem. We previously used iwgen to generate output within scripts. We are now trying to use the XalanTransform.exe for the XSL, but the problem we are running into is that are DCRs are being generated with the following DOCTYPE element:

<!DOCTYPE record SYSTEM "dcr4.5.dtd">

When the Xalan processor attempts to validate the DCR, it fails because the DTD doesn't exist in the same directory as the DCR. Apperantly iwgen doesn't do this validation.

Is there a way to include the full path to the DTD in the DCR when it is generated?

Thanks in advance.

Find more posts tagged with

Comments

moonkhanna

We recently converted from TPL PTs to XSL PTs and have run into a problem. We previously used iwgen to generate output within scripts. We are now trying to use the XalanTransform.exe for the XSL, but the problem we are running into is that are DCRs are being generated with the following DOCTYPE element:

When the Xalan processor attempts to validate the DCR, it fails because the DTD doesn't exist in the same directory as the DCR. Apperantly iwgen doesn't do this validation.

Is there a way to include the full path to the DTD in the DCR when it is generated?

Thanks in advance.

Not sure if what you suggest is a solution but for what you suggest you can do a search and replace of the string dcr4.5.dtd with path to the dtd...

Second option would be to put the dtd into the data folder of all your templates

ISCBorisB

We recently converted from TPL PTs to XSL PTs and have run into a problem. We previously used iwgen to generate output within scripts. We are now trying to use the XalanTransform.exe for the XSL, but the problem we are running into is that are DCRs are being generated with the following DOCTYPE element:

<!DOCTYPE record SYSTEM "dcr4.5.dtd">

When the Xalan processor attempts to validate the DCR, it fails because the DTD doesn't exist in the same directory as the DCR. Apperantly iwgen doesn't do this validation.

Is there a way to include the full path to the DTD in the DCR when it is generated?

Thanks in advance.

"dcr4.5.dtd" implies that you have DCRs in the IWOV Format, at least some of them. Do you? I *think* you'll need DCRs in XML Format to use XSL,
in that case you can control DCRs doctype format yourself or can go without it altogether. In IWOV mode moonkhanna's "copy DTD to data" proposal
seems to be just about the only thing you can do

Note that there are no IWOV-XML DCR Converter, you'd have to code it according to your XML DTD or do it manually.

Abishk

In IWOV mode moonkhanna's "copy DTD to data" proposal
seems to be just about the only thing you can do.

I was also facing the same problem and placing the dcr4.5.dtd in all the data folders wasn't a possible solution for me since then we had to restrict the authors from creating folders inside the data folder or make them copy this dtd file every time they create a folder inside data. So i went in for a global setting:-
-->i changed the reference of the dcr4.5.dtd to iw-home/local/config/dcr4.5.dtd in the dc_iwov_item_serializer.js file inside iw-home/httpd/webapps/content_center/datacapture folder
--> i need to know if someone has done this before and what could be the impact of this change. Only then will i be able to go ahead with this change.

Thanks a lot in advance.

Teamsite 7.1 Windows 2003 platform

Adam Stoller

The most likely impact is that you may have to make the same change over and over again anytime you upgrade TeamSite - that, and changing the file explicitly (rather than a copy of the file within IWHOME/local/config/lib/content_center/customer_src/) is completely unsupported.