Xalan is essentially using the standard package from the XML-Commons Apache project, packaging it as xml-apis.jar
Xerces also uses the files from that source, but trims away those which they don't think they need, to produce their xmlParserAPIs.jar.
Theoretically, if the former is on your classpath you shouldn't need the latter (assuming your Xerces and Xalan are otherwise in synch.)
The question of whether saving the bytes in xmlParserAPIs.jar is really worth the cost of having another jarfile to worry about is an ongoing debate.
______________________________________
Joe Kesselman / IBM Research
- Re: Xerces and Xalan packaging Joseph Kesselman
- Re: Xerces and Xalan packaging Shane Curcuru
