I know it may not be the most elegant way to retrieve the DTD info by forcing xerces to parse some fake String and append the DTD filename like this. I avoided putting the DTD filename in the parsed text by implementing my own caching EntityResolver but it would only make the sample more confusing if added here.
Look at the main method to see how to plug it into Xerces. You may also drop the LexicalHandler interface if you do not need to retrieve the comments. It have been tested on Xerces 1.3.0 and 1.3.1 but i belive it will also work on any 1.4.x Adam ----- Original Message ----- From: "Artur Lorincz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 07, 2001 8:22 AM Subject: Re: DTD parsing > Thank you. Actually I am using this DTD parser now. And I want to switch to > xerces. > > thanks, > Artur > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
SimpleDTDLister.java
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
