RE: [SOAP-JMS] Last Call comment LC08

(This is a resend; the previous one somehow did not make it to the public mailing list.)

 

Hi Roland, 
  
The changes do resolve the concerns I had. 
  
Thanks, 
Dongbo

 

 

________________________________

From: public-soap-jms-request@w3.org [mailto:public-soap-jms-request@w3.org] On Behalf Of Roland Merrick
Sent: Wednesday, April 22, 2009 12:27 PM
To: dongbo.xiao@oracle.com
Cc: Michael Chen; public-soap-jms@w3.org
Subject: RE: [SOAP-JMS] Last Call comment LC08

 


Greetings Dongbo, the URI Scheme for Java(tm) Message Service 1.0 [1] includes the following statement  -- The three recognized variants (<jms-variant> above) are "jndi", "queue", and "topic". -- but is does not require support for all recognized variants. The bindings spec does now make clear that only the jndi variant must be supported for a SOAP-JMS binding. 

We have corrected the use of "topicReplyToName" and added a new fault "unsupportedLookupVariant" to address the additional problems you pointed out. The latest editor draft [2] includes all the changes made to address the problems you identified. 

Please confirm whether the changes we have made satisfy the concerns that you raised. 

[1] http://www.ietf.org/internet-drafts/draft-merrick-jms-uri-05.txt <http://www.ietf.org/internet-drafts/draft-merrick-jms-uri-05.txt>  
[2] http://dev.w3.org/2008/ws/soapjms/soapjms.html <http://dev.w3.org/2008/ws/soapjms/soapjms.html>  

Regards, Roland




From: 

"Dongbo Xiao" <dongbo.xiao@oracle.com> 

To: 

Roland Merrick/UK/IBM@IBMGB 

Cc: 

"Michael Chen" <MICHAEL.X.CHEN@oracle.com>, "public-soap-jms@w3.org" <public-soap-jms@w3.org> 

Date: 

10/02/2009 16:53 

Subject: 

RE: [SOAP-JMS] Last Call comment LC08

 

________________________________




Hi Roland and the W3C SOAP/JMS working group, 
  
Thank you very much for taking my comments into consideration. 
  
The added clarification does serve the purpose of making it clear that the jndi variant is MUST supported by a conforming implementation, and other two variants are optional.  I am not sure then if this is consistent with Conformance-1002 <http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#Conformance-1002>  "Conforming implementations MUST implement all the requirements of [URI Scheme for JMS <http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#jmsuri> ]." 
  
My next question would be whether we need to specify how to interpret the additional query parameters that are specific to the two optional variants if an implementation decides to support them as well.  For example, the JMS URI scheme indicates that with "topic" variant, "topicReplyToName" should be used, in stead of "replyToName", while the binding spec (properties section and WSDL binding) does not discuss this at all. 
  
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. 
  
Regards, 
Dongbo 
  

 

________________________________


From: public-soap-jms-request@w3.org [mailto:public-soap-jms-request@w3.org <mailto:public-soap-jms-request@w3.org> ] On Behalf Of Roland Merrick
Sent: Wednesday, February 04, 2009 7:11 AM
To: Dongbo Xiao
Cc: Michael Chen; public-soap-jms@w3.org
Subject: [SOAP-JMS] Last Call comment LC08 
  

Greetings Dongbo, in your feedback you included the following comment which he have assigned the identifier: LC08 [1]. 

1. General Comments 

The JMS URI Scheme spec defines there variants: "jndi", "queue", and "topic". It is not clear whether all three variants have to be supported by a conforming implementation of the binding spec. If "queue and "topic" variant have to be supported as well, it would make sense to discuss the meaning of the relevant properties (for example, destinationName and replyToName) in the cases where the jms-variant is "queue" or "topic". 

The description of the soapjms:lookupVariant in 2.2.1, Connection to a destination has been updated by adding "The jms-variant: jndi MUST be supported." The latest version of the editor draft includes the change [2]. 

Please confirm whether the change we have made satisfies the concern that you raised. 
 
[1] http://www.w3.org/2002/ws/soapjms/wiki/2009-01_LC_Comments#LC08 <http://www.w3.org/2002/ws/soapjms/wiki/2009-01_LC_Comments#LC04>  
[2] http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#binding-connection <http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#binding-connection>  

Regards, Roland

 

________________________________


  

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 










________________________________

 

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