I'm curious. I haven't made provision for a SOAP fault in my WSDL but,
when I call a service in such a way that it generates an exception, the
Axis SOAP Monitor does not show the response message - but I can see
through a sniffer I've got running that there is actually a returned
SOAP message generated. The HTTP Header includes "HTTP/1.1 500 Internal
Server Error." but it is then actually followed by a SOAP message
including the following.
"<soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>..."
etc.
Is there any reason that this doesn't show up in the SOAP Monitor?
Should the Axis-generated WSDL include application exceptions that may
be thrown as SOAP faults? The exception that has been thrown is in fact
one I hadn't caught in the code. I'm not too clear on fault generation
with SOAP and would much appreciate any comments anyone might have on this.
Thanks.
Madeleine
