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

Derek

No fault subcode is defined for soapjms:soapAction

State:

CLOSED

Product:

Raised by:

Derek Rokicki

Opened on:

2010-09-14

Description:

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.

Related Actions Items:

No related actions

Related emails:

1. Re: Re : ACTION-214 Raise JIRA on CXF for latest fault code spec. changes (from eric@tibco.com on 2010-10-05)
2. Re : ACTION-214 Raise JIRA on CXF for latest fault code spec. changes (from peaston@progress.com on 2010-10-05)
3. Agenda for 2010-09-21 conference call (from eric@tibco.com on 2010-09-20)
4. ACTION-211 (from M8PHILLI@uk.ibm.com on 2010-09-15)
5. ISSUE-63 (Derek): No fault subcode is defined for soapjms:soapAction (from sysbot+tracker@w3.org on 2010-09-14)

Related notes:

Display change log