You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by James Heffernan <mi...@hotpop.com> on 2003/08/04 00:24:56 UTC
SAXException
Hi,
I'm a bit perplexed by this one. We had a webservice running fine and the
client I built using axis wsdl2java working with it just fine, until about a
week ago. Now on the first call to the service I get a RemoteException
thrown, and a stackTrace print shows a SAXException deserializing.
The response itself is very basic, it holds a simple enumerator class which
consists of a single String value.
It's a bit difficult to test unfortunately at the production site, as I need
to physically visit the site and run my test. However running the test class
here on my 'dummy' server (service generated from the same wsdl) works fine.
I've asked for a copy of the response soap message and all that I can see that
is different in it from the one returned here locally is this.
On the production system the envelope namespace is called soap: (so I get
elements like soap:Envelope and soap:Body). On my dummy service this is
called soapenv (so the corresponding elements are soapenv:Envelope and
soapenv:Body).
To me this would seem to be a problem but according to the administrator on
the production system he can see the requests arriving and the responses
leaving so the disparity does not seem to affect the service.
Does anyone know if this would be an issue or not? ( The production service
runs on IIS as a asmx page, my dummy service is deployed to Tomcat).
Thanks
James
(Axis 1.1 by the way)