Title: RE: Alternative location for DTDs

I answered this a little hastily. You could simply locate your DTD in a central place (say a WEB server) and have all your references to it by the central URL.

 

You still might want to look at Entity Resolver though. I have found that providing a caching entity resolver significantly improves performance.

 

Chris Raber, Systems Engineer, AvantGo Inc.

http://www.avantgo.com/

 

-----Original Message-----
From: Christopher Raber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 05, 2001 12:48 PM
To: 'Lajos Moczar'; '[EMAIL PROTECTED]'
Subject: RE: Alternative location for DTDs

 

You can provide your own entity resolver. This can improve performance too!

Chris Raber, Systems Engineer, AvantGo Inc.
 http://www.avantgo.com/

-----Original Message-----
From: Lajos Moczar [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 05, 2001 12:39 PM
To: [EMAIL PROTECTED]
Subject: Alternative location for DTDs

Hi all -

This problem is driving me crazy. I have a bunch of xml files to process
with Xalan, each in a separate dirctory. All the XMLs have a DTD
declaration like this:

<!DOCTYPE FRUID_XML_Tree SYSTEM "mydoc.dtd">

The problem is that I don't want to have to copy mydoc.dtd into each
directory. Ideally, I'd like to ignore the DTD declaration, but
alternatively I need to at least be able to tell Xalan to look for the
dtd in a different directory (like the directory where the xsl file is).
Originally, I thought that I could use a custom URIResolver for this,
but it appears that the URIResolver is not called to resolve DTD locations.

Can anyone suggest anything? I have this problem with serveral different
applications and I'm at a loss as to what to do.

Regards,

Lajos

Reply via email to