Yes, xalan.jar does not want jaxp.jar and parser.jar (which may contain old
DOM/SAX/JAXP classes) in the classpath, so although it sounds odd, the best
thing to do is remove jaxp.jar and parser.jar from the classpath *or from
any other location that your JVM uses for extension or bootclasspath
.jars*!
Different JVM's automagically load. jar files from the extensions and other
areas even though you didn't specify them on your classpath. This has been
discussed here several times.
Yes, there may be a difference in behavior between 2.0.1 and 2.1, since we
actually improved our JAXP classes that we ship inside of xalan.jar;
however having the old JAXP classes in the extensions directory causes this
to break.
- Shane
(Sorry for short reply, I'm getting fed up with slow modem at hotel!)
