...

Networking - SOAP

Back to Course

Lesson Description


Lession - #1369 SOAP Fault


SOAP FAULT

If an error occurs all through processing, the reaction to a soap message is a soap fault detail in the body of the message, and the fault is returned to the sender of the soap message. The soap fault mechanism returns precise records approximately the mistake, consisting of a predefined code, a description, and the cope with of the cleaning soap processor that generated the fault.

Points to Note

  • A SOAP message can carry only one fault block.
  • Fault is an optional part of a SOAP message.
  • For HTTP binding, a successful response is linked to the 200 to 299 range of status codes.
  • SOAP Fault is linked to the 500 to 599 range of status codes.


Sub-elements of fault


Sr.No Sub-element & Description
1

<faultCode>

It is a text code used to indicate a class of errors. See the next Table for a listing of predefined fault codes.

2

<faultString>

It is a text message explaining the error.

3

<faultActor>

It is a text string indicating who caused the fault. It is useful if the SOAP message travels through several nodes in the SOAP message path, and the client needs to know which node caused the error. A node that does not act as the ultimate destination must include a faultActor element.

4

<detail>

It is an element used to carry application-specific error messages. The detail element can contain child elements called detail entries.


SOAP Fault Codes


Sr.No Error & Description
1

SOAP-ENV:VersionMismatch

Found an invalid namespace for the SOAP Envelope element.

2

SOAP-ENV:MustUnderstand

An immediate child element of the Header element, with the mustUnderstand attribute set to "1", was not understood.

3

SOAP-ENV:Client

The message was incorrectly formed or contained incorrect information.

4

SOAP-ENV:Server

There was a problem with the server, so the message could not proceed.


SOAP Fault Example


The following code is a sample Fault. The consumer has asked a technique named ValidateCreditCard, however the provider does not assist such a way. This represents a customer request mistakes, and the server returns the following soap reaction −

    
<?xml version = '1.0' encoding = 'UTF-8'?>
<SOAP-ENV:Envelope
   xmlns:SOAP-ENV = "http://schemas.xmlsoap.org/soap/envelope/"
    
   xmlns:xsd >

   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode xsi:type = "xsd:string">SOAP-ENV:Client</faultcode>
         <faultstring xsi:type = "xsd:string">
            Failed to locate method (ValidateCreditCard>
in class (examplesCreditCard>
at /usr/local/ActivePerl-5.6/lib/site_perl/5.6.0/SOAP/Lite.pm line 1555.
</faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope>