>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*!
jaxp.jar and parser.jar WASN'T in the CLASSPATH. They were just next
to xalan.jar (and xerces.jar) (ie in the same directory).
When I copied xerces.jar and xalan.jar, to a new directory,
the problem disappears.
>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.
I know that but the jaxp/parser wasn't in jre/lib/ext or others
MAGIC directory.
>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.
The question is WHY xalan load a .jar not specified in the CLASSPATH ?
