Differences between revisions 1 and 2
Revision 1 as of 2004-12-28 18:36:38
Size: 1152
Editor: RickKellogg
Comment:
Revision 2 as of 2009-09-20 22:49:06
Size: 1156
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Axis needs an XML parser implementing the [http://java.sun.com/xml/jaxp/ JAXP 1.1] specification. It needs to be a fairly complete parser, as SOAP uses XML Schema and namespaces everywhere. Axis needs an XML parser implementing the [[http://java.sun.com/xml/jaxp/|JAXP 1.1]] specification. It needs to be a fairly complete parser, as SOAP uses XML Schema and namespaces everywhere.
Line 6: Line 6:
'''The parser that Axis is primarily built and tested against it is [http://xml.apache.org/xerces2-j/ Xerces].''' Other implementations of the XML Parser APIs may look the same to many apps, but cause Axis to choke with obscure errors. We have seen this with Crimson, Caucho, Aelfred and the Oracle parser implementations. Java 1.4 includes Crimson. '''The parser that Axis is primarily built and tested against it is [[http://xml.apache.org/xerces2-j/|Xerces]].''' Other implementations of the XML Parser APIs may look the same to many apps, but cause Axis to choke with obscure errors. We have seen this with Crimson, Caucho, Aelfred and the Oracle parser implementations. Java 1.4 includes Crimson.

XML Parser Notes

Axis needs an XML parser implementing the JAXP 1.1 specification. It needs to be a fairly complete parser, as SOAP uses XML Schema and namespaces everywhere.

The parser that Axis is primarily built and tested against it is Xerces. Other implementations of the XML Parser APIs may look the same to many apps, but cause Axis to choke with obscure errors. We have seen this with Crimson, Caucho, Aelfred and the Oracle parser implementations. Java 1.4 includes Crimson.

If you are having problems with Axis, and using any parser other than Xerces, try switching to Xerces to see if it goes away.

Also, Axis wants only one parser on the classpath. If you have multiple implementations of an XML parser in the path, you are going to get in trouble. This goes for many other XML applications. Errors like class cast exceptions, or complaints about missing methods in org.w3c classes are common symptoms. Track down where your parsers are coming from, and settle on the one parser that you want. Xerces, preferably.

FrontPage/Axis/Install/Diagnostics/XMLParsers (last edited 2009-09-20 22:49:06 by localhost)