Adam Lally wrote:
...
For the curious... The reason is because IBM's Java bundles Xerces
already. So adding xercesImpl.jar to the classpath just adds classes
with the same class names as those already bundled in the JRE. The -D
argument cannot be used to distinguish them. The ones in the JRE take
precedence. About the only way I could think to work around this
would be to go into your JRE install directory and remove xml.jar.
But it's probably better to just not use this buggy JRE at all. Sun's
Java bundles a different XML parser with different class names, and
doesn't have this problem. Also in Java 5 they finally realized this
problem and renamed the XML parser classes when bundling them, so that
they can be overridden.
-Adam
FYI, you can make the IBM JVM use your jars before its own like this:
-Xbootclasspath/p:/path/to/xercesImpl.jar
--Thilo
