ServerSOAPFaultException and how to read it?
I made a request and my program spat out
WARNING: Input Action on WSDL operation Search and @Action on its associated Web Method search did not match and will cause problems in dispatching the requests
Exception in thread "main" com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Client error Please see the server log to find more detail regarding exact cause of the failure.
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:124)
at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238)
....
I can see through mitmproxy that the server sent back
<?xml version='1.0' encoding='utf-8'?>
<!--pageview_candidate-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Client</faultcode>
<faultstring>Client error</faultstring>
<faultactor>http://api.bing.net:80/soap.asmx</faultactor>
<detail>
<Errors xmlns="http://schemas.microsoft.com/LiveSearch/2008/03/Search">
<Error>
<Code>1001</Code>
<Message>Required parameter is missing.</Message>
<HelpUrl>http://msdn.microsoft.com/en-us/library/dd251042.aspx</HelpUrl>
<Parameter>SearchRequest.AppId</Parameter>
</Error>
<Error>
<Code>1001</Code>
<Message>Required parameter is missing.</Message>
<HelpUrl>http://msdn.microsoft.com/en-us/library/dd251042.aspx</HelpUrl>
<Parameter>SearchRequest.Sources</Parameter>
</Error>
</Errors>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
How can I read the first bit and get the details in the second bit? I don't have access to the server log like the log on the server hosting the web service.
I noticed that xml elements inside soapenv: Fault don't have xmlns. Is this how most SOAP errors are reported back? Is this a non-standard way to do something? Do I have to rely entirely on mitmproxy to debug these problems using webservices?
source to share
You have to create a SOAPHandler to catch the SOAP response / error.
Use this tutorial to learn how to create a handler and register it with a service port:
http://www.mkyong.com/webservices/jax-ws/jax-ws-soap-handler-in-client-side/
Then don't forget to override the handleFault (SOAPMessageContext) method to catch server errors.
source to share