Are You Recruiter/Hiring Manager

*Filter candidates using TestYourCandidate.com and save 80% time ( saving time for recruiters and interviewers)
*More than 50% candidates can be filtered on Candidate Screening online tests
*Inbuilt exams are available in library, created and tested by experts Try Today...

When a MESSAGE contains a soap:Fault element its element children MUST be unqualified.

CORRECT:

<soap:Fault xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'
xmlns='' >
<faultcode>soap:Client</faultcode>
<faultstring>Invalid message format</faultstring>
<faultactor>http://example.org/someactor</faultactor>
<detail>
<m:msg xmlns:m='http://example.org/faults/exceptions'>
There were <b>lots</b> of elements in the message that
I did not understand
</m:msg>
</detail>
</soap:Fault>

INCORRECT (child elements have namespace prefixes):

<soap:Fault xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' >
<soap:faultcode>soap:Client</soap:faultcode>
<soap:faultstring>Invalid message format</soap:faultstring>
<soap:faultactor>http://example.org/someactor</soap:faultactor>
<soap:detail>
<m:msg xmlns:m='http://example.org/faults/exceptions'>
There were <b>lots</b> of elements in the message that
I did not understand
</m:msg>
</soap:detail>
</soap:Fault>

A RECEIVER MUST accept fault messages that have any number of ELEMENTS, including zero, appearing as children of the
detail element. Such children can be qualified or unqualified.

A RECEIVER MUST accept fault messages that have any number of qualified or unqualified ATTRIBUTES, including zero,
appearing on the detail element. The namespace of qualified attributes can be anything
other than "http://schemas.xmlsoap.org/soap/envelope/".

A RECEIVER MUST accept fault messages that carry an xml:lang attribute on the faultstring element.

When a MESSAGE contains a faultcode element the content of that element SHOULD be one of the fault codes
defined in SOAP 1.1 or a namespace qualified fault code.

SOAP 1.1 defines following faultcode values:

Table 2.3. SOAP Fault Codes

Error

Description

VersionMismatch

The processing party found an invalid namespace for the SOAP Envelope element.

MustUnderstand

An immediate child element of the SOAP Header element that was either not understood
or not obeyed by the processing party contained a SOAP mustUnderstand attribute with a value of
"1".

Client

The Client class of errors indicate that the message was incorrectly formed or did not contain the appropriate
information in order to succeed. For example, the message could lack the proper authentication or payment
information. It is generally an indication that the message should not be resent without change.

Server

The Server class of errors indicate that the message could not be processed for reasons not directly attributable
to the contents of the message itself but rather to the processing of the message. For example, processing could
include communicating with an upstream processor, which didn't respond. The message may succeed at a later point
in time.

When a MESSAGE contains a faultcode element the content of that element SHOULD NOT use of
the SOAP 1.1 "dot" notation to refine the meaning of the Fault.