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

Re: [SOAP-JMS] last call comment : LC04

From: Phil Adams <phil_adams@us.ibm.com>
Date: Wed, 21 Jan 2009 13:10:54 -0600
To: Roland Merrick <roland_merrick@uk.ibm.com>
Cc: public-soap-jms@w3.org, public-soap-jms-request@w3.org
Message-ID: <OF03713057.61AE0F72-ON86257545.0068F47B-86257545.00695F05@us.ibm.com>
Hi Roland,
Unless I'm misunderstanding this, "destinationName" is not an actual 
property that appears in the JMS URI (in the property=value form). 
Instead, "destinationName" represents the value that follows the 
"jms:jndi:" prefix (scheme and variant values).   So, I'm not sure what 
would be gained by calling it "jndiDestinationName".   That would have no 
affect on the JMS URI per se.


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

Roland Merrick <roland_merrick@uk.ibm.com>
01/21/2009 05:27 AM
[SOAP-JMS] last call comment : LC04

Greetings, I have taken a look at comment LC04 (**comment3 from Tang, 
Yong-Ping). In this he asks why jndiConnectionFactoryName is prefixed by 
jndi, but destinationName is not. 

The simple answer is that destinationName is used with any lookup variant 
not just for jndi. Perhaps we need to make this clearer. I think we should 
also consider one or more FAQs to deal with looking up connection details 
for a destination. We do have some material on this in the JMS URI spec. 

Regards, Roland

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 
Received on Wednesday, 21 January 2009 19:11:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:20 UTC