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

ACTION-134 - propose alternate wording to resolve ISSUE-26

From: Eric Johnson <eric@tibco.com>
Date: Mon, 01 Feb 2010 16:26:46 -0800
Message-ID: <4B677146.2010900@tibco.com>
To: SOAP-JMS <public-soap-jms@w3.org>
The current proposal is in the issue:
http://www.w3.org/2002/ws/soapjms/tracker/issues/26

New proposed resolution:

In section 3.4.5, change this paragraph:

This URI is found as the value of the location attribute on the
<wsdl11soap11:address>  or <wsdl11soap12:address>  element when using
SOAP 1.1 and SOAP 1.2, respectively. The value of the location attribute
MUST be a URI corresponding to a JMS Destination, and SHOULD be a "jms"
scheme URI.

to this:

This URI is found as the value of the location attribute on the
<wsdl11soap11:address>  or <wsdl11soap12:address>  element when using
SOAP 1.1 and SOAP 1.2, respectively. The value of the location attribute
MUST be a URI corresponding to a JMS Destination, and SHOULD be a "jms"
scheme URI.  The values for parameters in the URI needs to be encoded
("%20" for space, for example) as per normal URI escaping rules, and the
resulting URI needs to be encoded as per normal XML rules ("&amp;" for
&) when serialized into an XML attribute.

---
(That is, add a new sentence to the end of the paragraph.)

Also, in the example, change:
   <wsdl11soap11:address
location="jms:jndi:destinationName?targetService=service1"/>

to
   <wsdl11soap11:address
location="jms:jndi:destinationName?targetService=service%20Test&amp;priority=5"/>


---
(An example of each form of proper encoding)
Received on Tuesday, 2 February 2010 00:27:34 GMT

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