----- Original Message ----- From: "Pascale, Peter H." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 13, 2003 11:16 Subject: xerces.jar vs. xercesImpl.jar
> I am surprised to find that axis seems to require a specific parser - > xerces, and will not accept xercesImpl. I thought both would be JAXP 1.1 > compliant parsers, as the set-up instructions describe: It does not require a specific parser, merely recommends ones that work. Lots of them seem to have problems with complex XML Schema. Xerces is the one that Axis is primarily tested against; crimson, caucho and the oracle one all have caused problems in the past. So the issue is not JAXP1.1 compliance, as compliance with the XML and XSD specificiations. > > > "In the WEB-INF directory, you'll find a "lib" directory. > > In this directory, copy the jars associated with the JAXP 1.1 XML compliant > parser of your choice. We recommend xerces jars from the xml-xerces > distribution, though others work." see: a recommendation, not a requirement. > > When I try to compile wsdl or run an axis client with xercesImpl.jar in the > classpath instead of xerces.jar, I get: > > [java] java.lang.NoClassDefFoundError: org/w3c/dom/Node > > Any ideas why this incompatibility exists? You have multiple implementations of XML parsers in your classpath
