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

ISSUE-26 (mphillip): Encoding URI parameters for use in WSDL [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 25 Jan 2010 17:25:10 +0000 (GMT)
To: public-soap-jms@w3.org
Message-Id: <20100125172510.D1528C6DB9@barney.w3.org>

ISSUE-26 (mphillip): Encoding URI parameters for use in WSDL [SOAP-JMS Binding specification]

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

Raised by: Mark Phillips
On product: SOAP-JMS Binding specification

When using multiple query parameters on a URI in WSDL documents, the parameter separator '&' needs to be escaped to ensure valid XML.  This is not immediately obvious and is not mentioned in the specification..  

Proposal:

In section 3.4.5, add a new final paragraph:

If more than one property is used in a URI, then the URI query parameters will be separated by an ampersand.  To ensure that this ampersand does not invalidate the XML document, it MUST be escaped with the "&amp" XML character reference.  This is true for any of the character entities that require special encoding in XML (e.g. &, <,>, ',").    (This is in addition to any URI encoding though this is arguably covered in the URI spec).  We should make this clearer with at least one example showing multiple properties in a WSDL URI, and possibly a property showing URI encoding. 

Change: 

  <wsdl11soap11:address location="jms:jndi:destinationName?targetService=service1"/> 

to: 

  <wsdl11soap11:address location="jms:jndi:destinationName?targetService=service1&amp;priority=5&amp;userAddress=5%20Main%20Street"/> 
Received on Monday, 25 January 2010 17:25:12 GMT

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