http://www.ibm.com/schema/soa/fltalm/v1_1/local
The recordFaultRequest Complex Type

Record fault request type.


Local elements (7)
globalTransactionID service source code severity message detail
Complex Type recordFaultRequest
The recordFaultRequest type does not allow mixed content. There is no restriction on type derivation. 
 CollapseClick here to hide comment XML Instance
<...>
-Begin Sequence [1...1]

The global transaction ID for the Web Service transaction. The length of this identifier should be less that 128 if CEI is enabled.

<globalTransactionID>xsd:string</globalTransactionID> [1..1]

The service implementation that originated the fault. The service name is specific to each service implementation and should be chosen to avoid conflicts with other service implementations.

<service>xsd:string</service> [1..1]

The source of the fault. The suggested format is: <server_name>:<ear_name>:<class_name>

<source>xsd:string</source> [1..1]

The code describing the fault. This code should match the message code used to output the logging message associated with the fault. This provides synchronization between documented message codes and fault information.

<code>xsd:string</code> [1..1]

The severity of the fault.

<severity>twss_fltalm_xsd:SeverityEnumeration</severity> [1..1]

The fault message.

<message>xsd:string</message> [1..1]

Operation detail information (such as a stack trace) regarding the fault.

<detail>xsd:string</detail> [0..1]
End Sequence
</...>

 Collapse Attributes

Name Type Summary
No Attributes

 Collapse XML
-<xsd:complexType  name="recordFaultRequest">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>Record fault request type.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
-<xsd:sequence>
-<xsd:element  name="globalTransactionID"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The global transaction ID for the Web Service transaction. The length of this identifier should be less that 128 if CEI is enabled.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="service"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The service implementation that originated the fault. The service name is specific to each service implementation and should be chosen to avoid conflicts with other service implementations.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="source"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The source of the fault. The suggested format is: <server_name>:<ear_name>:<class_name></xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="code"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The code describing the fault. This code should match the message code used to output the logging message associated with the fault. This provides synchronization between documented message codes and fault information.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="severity"  type="twss_fltalm_xsd:SeverityEnumeration">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The severity of the fault.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="message"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The fault message.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  maxOccurs="1"  minOccurs="0"  name="detail"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>Operation detail information (such as a stack trace) regarding the fault.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

 Collapse Uses
 Collapse Type (2)
 
 Collapse Used-By
 Collapse Element (1)
 
Generated by WSDLdoc ©