Any good hints on how to go about debugging SAX exceptions? For example, how to at least decide if the problem is:

a) a bug in Axis
b) a bug in SAX
c) malformed WSDL
d) malformed XML data

For example my Axis 1.3 client is currently reporting:

org.xml.sax.SAXException: Invalid element in com.jarmo.MyClass - myField
at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
       at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
       at org.apache.axis.client.Call.invoke(Call.java:2467)
       ...

As far as I can tell, and wsdl2java/java2wsdl are concerned, my WSDL is fine and the SOAP monitor shows what I'd expect. The field in question is a string, just as many of my other fields are and they don't exhibit the same problem.

PS please could someone reassure me that I'm not making a terrible mistake in using Axis 1.3 for server (and test client) development. It is a reasonably solid platform for (doc/lit) web services development, right? I ask because I continue to run into problems and almost without exception they don't make much sense and waste enormous amounts of time (like the problem I describe here).

Thanks.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Reply via email to