W3C home > Mailing lists > Public > public-soap-jms@w3.org > September 2010

ISSUE-63 (Derek): No fault subcode is defined for soapjms:soapAction

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 14 Sep 2010 15:55:08 +0000
To: public-soap-jms@w3.org
Message-Id: <E1OvXqe-0001KJ-8a@crusher.w3.org>

ISSUE-63 (Derek): No fault subcode is defined for soapjms:soapAction

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

Raised by: Derek Rokicki
On product: 

The specification states that soapjms:soapAction must be included in the message properties when specified. However, no fault subcode is defined for this scenario.

The proposed resolution is to modify section 2.2.3. The section currently includes:

[Definition: soapjms:soapAction] (xsd:anyURI)
* as with SOAP/HTTP
* optional in WSDL, optional in environment
* if specified MUST appear in the JMS message in the JMS property named SOAPJMS_soapAction.  
* if using SOAP 1.2, and the contentType property has an action parameter, that parameter value MUST match this SOAPJMS_soapAction value.† [Definition: Use fault subcode mismatchedSoapAction if the SOAP 1.2 action does not match.†]

I suggest appending one of the following definitions to the third bullet point:

option 1 - [Definition: Use fault subcode missingSoapAction if specified in the WSDL and SOAPJMS_soapAction does not appear.]

option 2 - [Definition: Fault subcode missingSoapAction may be used if specified in the WSDL and SOAPJMS_soapAction does not appear.]

Additionally, missingSoapAction should be added to the subcode list in section 2.8, and Protocol-2018 should be modified accordingly.
Received on Tuesday, 14 September 2010 15:55:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:24 GMT