Re: ACTION-75: proposed change to binding spec

I missed that unfortunately... but yes, we need to add 
"unsupportedLookupVariant" as a new fault subcode in the list provided in 
section 2.8.     There's really no detail in that list; just a list of the 
subcodes defined throughout the binding spec.

Thanks, 
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





From:
Roland Merrick <roland_merrick@uk.ibm.com>
To:
Phil Adams/Austin/IBM@IBMUS
Cc:
public-soap-jms@w3.org, public-soap-jms-request@w3.org
Date:
04/14/2009 07:04 AM
Subject:
Re: ACTION-75: proposed change to binding spec
Sent by:
public-soap-jms-request@w3.org




Greetings Phil, looks fine as far as it goes, but surely we would also 
have to add something to 2.8 Faults [1] ? 

[1] 
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#binding-faults 


Regards, Roland
FBCS, CITP
IBM Software Group, Strategy, Software Standards
Tel/Fax: +44 (0)1926-465440
Mobile: +44 (0)77 2520-0620 


From: 
Phil Adams <phil_adams@us.ibm.com> 
To: 
public-soap-jms@w3.org 
Date: 
10/04/2009 21:38 
Subject: 
ACTION-75: proposed change to binding spec





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 









Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU