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

Fault sub-code QName

XML Schema should define fault sub-code QName types

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Peter Easton

Opened on:

2010-05-17

Description:

From email:
http://lists.w3.org/Archives/Public/public-soap-jms/2010May/0008.html

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"/>
</xs:restriction>
</xs:simpleType>

Related Actions Items:

No related actions

Related emails:

1. Agenda for the 2010-06-15 conference call (from eric@tibco.com on 2010-06-14)
2. Agenda for the 2010-06-08 conference call (from eric@tibco.com on 2010-06-07)
3. Agenda for the 2010-05-25 conference call (from eric@tibco.com on 2010-05-24)
4. Agenda for the 2010-05-18 conference call (from eric@tibco.com on 2010-05-17)
5. Re: Request To Raise Issue: soap-jms schema should define fault sub-code QName types (from eric@tibco.com 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 sysbot+tracker@w3.org on 2010-05-17)

Related notes:

Display change log