ISSUE-34 (Fault sub-code QName): XML Schema should define fault sub-code QName types [SOAP-JMS Binding specification]

• From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
• Date: Mon, 17 May 2010 20:25:10 +0000 (GMT)
• To: public-soap-jms@w3.org
• Message-Id: <20100517202510.E37D25F76D@stu.w3.org>

ISSUE-34 (Fault sub-code QName): XML Schema should define fault sub-code QName types [SOAP-JMS Binding specification]

http://www.w3.org/2002/ws/soapjms/tracker/issues/34

Raised by: Peter Easton
On product: SOAP-JMS Binding specification

>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>

Received on Monday, 17 May 2010 20:25:15 UTC