complexType "faultDetailType"
Namespace:
Content:
complex, 2 elements
Defined:
globally in hsinfra.xsd; see XML source
Includes:
definitions of 2 elements
Used:
never
XML Representation Summary
<...>
   
Content: 
</...>
Content Model Elements (2):
faultChain (type faultChainType), faultResponseAction (type xsd:string)
XML Source (see within schema source)
<xsd:complexType name="faultDetailType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="faultResponseAction" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
This is the response action that is to be taken by the client upon
receiving this fault message. Contents of this element can be:
<p/>
<dl>
<dt>
<b>correct</b>
</dt>
<dd>
A correctable error was detected. The client should reform the
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.
</dd>
<dt>
<b>retry</b>
</dt>
<dd>
A transient error has occured. The client should resubmit the message
(ensuring that a new message ID is used).
</dd>
<dt>
<b>giveUp</b>
</dt>
<dd>
An uncorrectable error was detected. The client should accept the failure
condition and execue appropriate recovery logic.
</dd>
</dl>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="1" name="faultChain" type="faultChainType">
<xsd:annotation>
<xsd:documentation>
When a request is being processed by a service, it may be traveling through multiple
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:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 2/2)
faultChain
Type:
faultChainType, complex content
Defined:
locally within (this) faultDetailType complexType
When a request is being processed by a service, it may be traveling through multiple 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.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="1" name="faultChain" type="faultChainType">
<xsd:annotation>
<xsd:documentation>
When a request is being processed by a service, it may be traveling through multiple
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:documentation>
</xsd:annotation>
</xsd:element>

faultResponseAction
Type:
xsd:string, predefined, simple content
Defined:
locally within (this) faultDetailType complexType
This is the response action that is to be taken by the client upon receiving this fault message. Contents of this element can be: <p/> <dl> <dt><b>correct</b></dt> <dd>A correctable error was detected. The client should reform the 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. </dd> <dt><b>retry</b></dt> <dd>A transient error has occured. The client should resubmit the message (ensuring that a new message ID is used). </dd> <dt><b>giveUp</b></dt> <dd>An uncorrectable error was detected. The client should accept the failure condition and execue appropriate recovery logic.</dd> </dl>
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="1" name="faultResponseAction" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
This is the response action that is to be taken by the client upon
receiving this fault message. Contents of this element can be:
<p/>
<dl>
<dt>
<b>correct</b>
</dt>
<dd>
A correctable error was detected. The client should reform the
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.
</dd>
<dt>
<b>retry</b>
</dt>
<dd>
A transient error has occured. The client should resubmit the message
(ensuring that a new message ID is used).
</dd>
<dt>
<b>giveUp</b>
</dt>
<dd>
An uncorrectable error was detected. The client should accept the failure
condition and execue appropriate recovery logic.
</dd>
</dl>
</xsd:documentation>
</xsd:annotation>
</xsd:element>