Never mind - it was determined that the client could understand the details element (nested custom exceptions) of the soap fault. This is the route we are going to take.
Type: Posts; User: emsworth; Keyword(s):
Never mind - it was determined that the client could understand the details element (nested custom exceptions) of the soap fault. This is the route we are going to take.
Is there a way to dynamically generate a WSDL with a fault element that does not include the soap element? I am currently generating something like this:
<wsdl:fault name="MyCustomFault">
...