- From: Roland Merrick <roland_merrick@uk.ibm.com>
- Date: Wed, 1 Apr 2009 15:34:09 +0100
- To: yong-ping.tang@hp.com
- Cc: public-soap-jms@w3.org, jinzhai.zhang@hp.com
- Message-ID: <OF76B4703C.6E521D81-ON8025758B.004FD1EF-8025758B.00500823@uk.ibm.com>
Greetings, we would like to complete our handling of issues raised during the Last Call process and to that end we would appreciate it if you could take a look at the attached and see if the response we have made satisfies the concern that you raised. An email to the WG mailing list public-soap-jms@w3.org with your feedback would be appreciated. Regards, Roland ----- Forwarded by Roland Merrick/UK/IBM on 01/04/2009 15:31 ----- From: Roland Merrick/UK/IBM@IBMGB To: yong-ping.tang@hp.com Cc: public-soap-jms@w3.org, jinzhai.zhang@hp.com Date: 29/01/2009 17:33 Subject: [SOAP-JMS] Last Call comment LC04 Greetings, in your feedback you included the following comment which he have assigned the identifier: LC04 [1]. **Comment3 Point: chapter 2.2.1 definition of destinationName and jndiConnectionFactoryName Comment: jndiConnectionFactoryName,destinationName,why first item with prefix ?jndi?, but second one without it? The jndiConnectionFactoryName (along with jndiInitialContextFactory, jndiURL and jndiContextParameter) are all the names of parameters (as in the name, value pairs) that can be specified on a JMS URI or element names in WSDL. The JMS URI syntax specifies a positional parameter --jms-dest -- to define the destination name and as such "destinationName" is only a label used in the SOAP-JMS Binding spec to refer to the value of the positional parameter jms-dest. The string "destinationName" never appears at run time, the nearest is the JMS Header field named JMSDestination that is derived from destinationName (or jms-dest). The reason that we do not prefix destinationName with "jndi" is because the positional parameter jms-dest in the URI applies to all variants and not just to the jndi variant. This is described in the URI Scheme for Java(tm) Message Service 1.0 [2]. The URI spec includes the following examples: jms:jndi:SomeJndiNameForDestination?jndiInitialContextFactory=com.example.jndi.JndiFactory&priority=3 jms:queue:ExampleQueueName?timeToLive=1000 in these examples the the jms-dest parameter (which we refer to as destinationName) are "SomeJndiNameForDestination" and "ExampleQueueName". >From this you can see that the name of the destination is not necessarily a jndi name. We have made no changes to the specification please confirm whether this explanation satisfies the concern that you raised. If you still feel that some change is necessary please let us know. [1] http://www.w3.org/2002/ws/soapjms/wiki/2009-01_LC_Comments#LC04 [2] https://datatracker.ietf.org/drafts/draft-merrick-jms-uri/ 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
Received on Wednesday, 1 April 2009 14:34:54 UTC