Servers should return http 500 when raising an exception but some do not. Suds (version
<= 0.3.9) will only detect the fault when seeing http 500. Fault detection was
enhanced
in 0.4 by searching the reply XML for faults even when http 200 is returned. Maybe you
can try 0.4 beta? If the server is raising an exception but not returning any evidence in
the response, you're probably out of luck.
On 05/25/2010 01:43 PM, Joshua J. Kugler wrote:
On Tuesday 25 May 2010, Donald W. Long elucidated thus:
> I found that if the service returns a string value and the service
> throws an exception i can look at the result and it will contain
> 'soap:Server', but if the service returns void then you can not tell
> if you have an error or not.
>
>
> But what I am really trying to figure out, is how do you see what
> exception the service has thrown.
>
> You may noticed that I am using the WindowsHttpAuthenticated, this is
> required for access to the server that is running the web services.
If you are not seeing a suds.WebFault raised then the service is not
raising a SOAPFault, and thus is returning error information to you
other ways. If the service does not raise a SOAPFault on errors, then
you will have to wrap the call and raise an exception if an error
condition is returned.
j