Namespace: |
|
Content: |
complex, 2 elements |
Defined: |
globally in hsinfra.xsd; see XML source |
Includes: |
definitions of 2 elements |
Used: |
never |
XML Representation Summary |
|||||
<...> |
|||||
|
|||||
</...> |
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="faultResponseAction" type="xsd:string">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This is the response action that is to be taken by the client upon
</xsd:documentation>
receiving this fault message. Contents of this element can be: <p/>
<dl>
<dt>
</dl>
<b>correct</b>
</dt>
<dd>
A correctable error was detected. The client should reform the
</dd>
request message, correcting the noted error, and resubmit the message. If the client is unable to correct the message, the client should accept the failure condition and execute approriate recovery logic. <dt>
<b>retry</b>
</dt>
<dd>
A transient error has occured. The client should resubmit the message
</dd>
(ensuring that a new message ID is used). <dt>
<b>giveUp</b>
</dt>
<dd>
An uncorrectable error was detected. The client should accept the failure
</dd>
condition and execue appropriate recovery logic.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
When a request is being processed by a service, it may be traveling through multiple
</xsd:documentation>
sections of the service code. The <b>faultChain</b>
element contains a list of errors if
there are multiple errors along the processing path of a message. Because a section of the service or the server may overwrite the error code with a more general error, this list gives a history of failures for this particular request. <p/>
<b>faultChain</b>
contains multiple
<b>fault</b>
elements. Each
<b>fault</b>
element
contains details about an error condition which this request has caused to occur during its processing. </xsd:complexType>
|
Type: |
faultChainType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
When a request is being processed by a service, it may be traveling through multiple
</xsd:documentation>
sections of the service code. The <b>faultChain</b>
element contains a list of errors if
there are multiple errors along the processing path of a message. Because a section of the service or the server may overwrite the error code with a more general error, this list gives a history of failures for this particular request. <p/>
<b>faultChain</b>
contains multiple
<b>fault</b>
elements. Each
<b>fault</b>
element
contains details about an error condition which this request has caused to occur during its processing. </xsd:element>
|
Type: |
xsd:string, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This is the response action that is to be taken by the client upon
</xsd:documentation>
receiving this fault message. Contents of this element can be: <p/>
<dl>
<dt>
</dl>
<b>correct</b>
</dt>
<dd>
A correctable error was detected. The client should reform the
</dd>
request message, correcting the noted error, and resubmit the message. If the client is unable to correct the message, the client should accept the failure condition and execute approriate recovery logic. <dt>
<b>retry</b>
</dt>
<dd>
A transient error has occured. The client should resubmit the message
</dd>
(ensuring that a new message ID is used). <dt>
<b>giveUp</b>
</dt>
<dd>
An uncorrectable error was detected. The client should accept the failure
</dd>
condition and execue appropriate recovery logic. </xsd:element>
|