On Wed, 2004-02-11 at 21:18, [EMAIL PROTECTED] wrote:
> Hello,
>
> Our application uses both SAX and DOM to parse XML streams. My current setup
> is that I rely on the standard XML-apis that come with JDK 1.4.x and only
> have the xercesImpl.jar in my normal classpath. This seems to work fine for
> parsing the SAX way, but fails when parsing DOM. When instantiating the
> Xerces JAXP DocumentBuilderFactory, it seems to refer to some DOM Level2
> Ranges extension. Is there any version of Xerces2-J that has a clear split
> between the DOM Level2 core and the extensions? I ask this since adding the
> xml-apis.jar to the JDK 1.4 endorsed API folder is beyond my control.
> Relying on Crimson is not an option since this one has a bug in DOCTYPE
> declarations with relative URLs.
I have always thought that putting stuff in the global JDK 1.4 endorsed
directory is a very ugly thing to do, as it affects the behaviour of
every application using that JDK.
It is much nicer to used the "endorsed override" mechanism. This is
per-app, and also doesn't need ROOT access (or "admin" for you windows
types).
This option to the JVM:
java -Djava.endorsed.dirs=${overrides} .....
will cause any libs in the specified overrides directory to override
stuff in the JDK.
Just put xerces/xalan/xml-apis etc in a dir and use the above option to
point to that dir.
Hope this solves your problem..
Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
