W3C home > Mailing lists > Public > public-soap-jms@w3.org > November 2009

Applied resolution for ISSUE-4 (ACTION-120)

From: Mark Phillips <M8PHILLI@uk.ibm.com>
Date: Mon, 16 Nov 2009 14:44:51 +0000
To: public-soap-jms@w3.org
Message-ID: <OFE51CD281.058CDB58-ON80257670.0049DAE9-80257670.005102D5@uk.ibm.com>

Dear All

I've applied the changes for ACTION-120 [1] / ISSUE-4 [2] as per the
proposal discussed in the minutes of 2009/10/27 [3].

Section 2.2.4:

The following text...
"The "Client treatment" column describes how the property should be treated
in the process of forming the soapjms:requestURI property. There are three
options for this column:
      As-is — the client SHOULD— leave the information in the URI as is.
      Should exclude — the client SHOULD exclude the information from the
      generated requestURI .
      Must exclude — the client MUST not include the information in the
      generated requestURI."
...was removed because it duplicates the details on requestURI in section

The following text...
"[Definition:  A fault MUST be generated with subcode malformedRequestURI
when the URI violates the expected syntax. †].
[Definition:  A fault MUST be generated with subcode
targetServiceNotAllowedInRequestURI when targetService parameter is
included in the requestURI). †]"
...was moved to section 2.2.3 which is where the requestURI property and
associated SOAP faults are described.


The updated binding spec is available here:

This is a link to view the differences from the previous XML Spec version:

...and this is a link to view the differences from the previous HTML

[1] http://www.w3.org/2002/ws/soapjms/tracker/actions/120

[2] http://www.w3.org/2002/ws/soapjms/tracker/issues/4

[3] http://www.w3.org/2009/10/27-soap-jms-minutes.html

Received on Monday, 16 November 2009 14:47:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:21 UTC