On Tuesday 30 March 2010, Martin Aspeli elucidated thus:
>> AxisFault
>> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
>> faultSubcode:
>> faultString: 213
This ^^^^^
>> faultActor:
>> faultNode:
>> faultDetail:
>> {http://acme.com/}SOAPException:<message>213</message>
> If the above is truly the data structure of the fault, then you
> should be able to get it via e.faultString.
I think the above is what the developer sees in his debugger when an
exception representing the fault is not raised. Then again, I can't
be 100% sure.
I don't see e.faultString in WebException. Did you mean
e.fault.faultString?
You might get that via e.fault.faultString. The point is, you shouldn't
have to parse faultDetail if the faulString is available as its own
attribute.
j
--
Joshua Kugler
Part-Time System Admin/Programmer
http://www.eeinternet.com
PGP Key:
http://pgp.mit.edu/ ID 0x73B13B6A