ISSUE-34: XML Schema should define fault sub-code QName types

Fault sub-code QName

XML Schema should define fault sub-code QName types

SOAP-JMS Binding specification
Raised by:
Peter Easton
Opened on:
From email:

The soap-jms schema(currently the schema is an attachment to Action 44) should be enhanced to include fault sub-codes.

For example:

<xs:simpleType name="FaultCodesType">
<xs:restriction base="xs:QName">
<xs:enumeration value="tns:contentTypeMismatch"/>
<xs:enumeration value="tns:malformedRequestURI"/>
<xs:enumeration value="tns:mismatchedSoapAction"/>
<xs:enumeration value="tns:missingContentType"/>
<xs:enumeration value="tns:missingRequestURI"/>
<xs:enumeration value="tns:unrecognizedBindingVersion"/>
<xs:enumeration value="tns:unsupportedJMSMessageFormat"/>

Related Actions Items:
No related actions
Related emails:
  1. Agenda for the 2010-06-15 conference call (from on 2010-06-14)
  2. Agenda for the 2010-06-08 conference call (from on 2010-06-07)
  3. Agenda for the 2010-05-25 conference call (from on 2010-05-24)
  4. Agenda for the 2010-05-18 conference call (from on 2010-05-17)
  5. Re: Request To Raise Issue: soap-jms schema should define fault sub-code QName types (from on 2010-05-17)
  6. ISSUE-34 (Fault sub-code QName): XML Schema should define fault sub-code QName types [SOAP-JMS Binding specification] (from on 2010-05-17)

Related notes:

Opened as per

Eric Johnson, 25 May 2010, 02:28:24

Accepted application of the resolution of this issue as per:

Eric Johnson, 21 Jun 2010, 23:38:56

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 34.html,v 1.1 2013-09-16 14:06:35 carine Exp $