Forum Discussion
msimmerson
14 years agoOccasional Contributor
Thanks to Smartbear support I have a solution to the issue.
The errors was with the returned SOAP Fault in the detail stanza. Whilst the fault is modelled in an XSD with a type Fault - in the containing WSDL it is wrapped into an exception element for example ConnectionException. It is this that should appear in the detail section as shown below. The ns namespace should be the appropriate namespace as declared in the WSDL and should be declared in the body or envelope tags of the SOAP fault.
Hope that helps others.
Cheers
Matt
<ns:ConnectionException>
<code>1000</code>
<message>Connection Request Failed XML Validation,
Correlation Id - 1 ,
Number - 1 ,
Cut-off timestamp - 2008-09-29T14:49:45 ,
Num retries - a ,
Wait Period - a ,
Type - 1RECONNECT</message>
<processId>1</processId>
<shortMessage>Invalid Request</shortMessage>
<time>2012-01-31T13:22:13.715+13:00</time>
</ns:ConnectionException>
The errors was with the returned SOAP Fault in the detail stanza. Whilst the fault is modelled in an XSD with a type Fault - in the containing WSDL it is wrapped into an exception element for example ConnectionException. It is this that should appear in the detail section as shown below. The ns namespace should be the appropriate namespace as declared in the WSDL and should be declared in the body or envelope tags of the SOAP fault.
Hope that helps others.
Cheers
Matt
<ns:ConnectionException>
<code>1000</code>
<message>Connection Request Failed XML Validation,
Correlation Id - 1 ,
Number - 1 ,
Cut-off timestamp - 2008-09-29T14:49:45 ,
Num retries - a ,
Wait Period - a ,
Type - 1RECONNECT</message>
<processId>1</processId>
<shortMessage>Invalid Request</shortMessage>
<time>2012-01-31T13:22:13.715+13:00</time>
</ns:ConnectionException>