- From: Mark Phillips <M8PHILLI@uk.ibm.com>
- Date: Thu, 8 Jul 2010 10:34:28 +0100
- To: public-soap-jms@w3.org
The proliferation of JMS URI formats demonstrates the need for standardisation. Here's a summary of the four main JMS URI variants that IBM has identified (in IBM and open source projects). I'm sure that there are more, for example BusinessWorks, WebLogic and other vendor products probably have their own subtle variants. The URI syntax is similar in some these variants, but differences in the names of the parameters still prohibits interoperability. The most common differences are in the choice of name for the persistence/deliveryMode property, and the name of the reply destination (replyToName, replyTo, replyToDestination, replyDestination) so I have shown these parameters in the example (in the cases where their names are known). Here are the URIs: URI Origin: W3C SOAPJMS Workgroup (current IETF proposal http://tools.ietf.org/id/draft-merrick-jms-uri-07.txt) Syntax: jms:[queue|topic|jndi]:jms-dest [?<property>=<value>&<property>=<value>&...] Example: jms:jndi:MYQUEUE?replyToName=REPLYQ&deliveryMode=PERSISTENT URI Origin: AXIS2 1.1 ( http://ws.apache.org/axis2/1_1/jms-transport.html ) Syntax: jms:/ jms-dest [ "?" param *( [ "&" param ] ) Example: jms:/MYQUEUE/pojoQ? Note: Can't find a definitive list of parameters URI Origin: WSIF URI (http://ws.apache.org/wsif/) Syntax: jms:/[queue| topic]?[<property>=<value>&<property>=<value>&...] Example: jms:/queue?destination=MYQUEUE&replyTo=REPLYQ&deliveryMode=PERSISTENT URI Origin: IBM WebSphere Application Server 5-6, WebSphere MQ, IBM CICS Syntax: jms:/[queue| topic]?<property>=<value>&<property>=<value>&... Example: jms:/queue?destination=MYQUEUE?replyDestination=REPLYQ&persistence=2 Regards: Mark
Received on Thursday, 8 July 2010 09:43:02 UTC