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

ACTION-75: proposed change to binding spec

From: Phil Adams <phil_adams@us.ibm.com>
Date: Fri, 10 Apr 2009 15:37:17 -0500
To: public-soap-jms@w3.org
Message-ID: <OF957E2F7C.79F39520-ON86257594.006DFA75-86257594.00714666@us.ibm.com>
Hi everyone,
A couple of weeks ago I took ACTION-75  which is to come up with a 
response to Dongbo Xiao's comment:
"A related minor issue is the need of defining the error/fault message 
that the client would get when it uses a URL that contains the "queue" or 
"topic" variant to access an implementation that does not support those 
variants."

After reading through the spec and specifically searching for places where 
we refer to the variants of the JMS URI scheme, I think we really only 
need to change one place.   In section 2.2.1, we discuss various 
"connection-related" properties, one of which is the lookupVariant:

[Definition: soapjms:lookupVariant ](xsd:string)
Specifies the technique to use for looking up the given destination name.
MUST be specified in the JMS URI, as the jms-variant portion of the 
syntax. † 
The jms-variant: jndi MUST be supported


My proposal would be to simply change 
        "The jms-variant: JNDI MUST be supported"
 to 
        "The jms-variant: JNDI MUST be supported 
               [Definition: Use fault subcode unsupportedLookupVariant if 
the JMS URI specifies a lookup variant that is not supported by the 
implementation]".

Comments?

Phil 
__________________________________________________________________________________________________________ 

Phil Adams (phil_adams@us.ibm.com)

WebSphere Application Server
Office: (512) 286-5041 (t/l 363)
Web Services Development
Cell: (512) 750-6599
IBM - Austin, TX


Received on Friday, 10 April 2009 20:38:01 GMT

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