[ebxmlms-develop] JMS URI proposal

[Ronald v. K. <rv...@ab...>]

All,

For the return-path of messages to be delivered in a JMS Queue, there
has been a discussion of a jms: uri. Whether a uri is right or wrong,
hermes uses it internally. There are several options (see
http://marc.theaimsgroup.com/?l=axis-dev&m=103617964921940&q=p3)

I'm in favour of using the JNDI based one, without the provider specific
things, so

jms:///queue?connectionFactory=<conn-factory-jndi-name>&destination=<dest-jndi-name>

Meaning, it's a queue (not a topic) with a connectionFactory that is
fetched by looking it up in the default initialcontext by the name of
<conn-factory-jndi-name>. The queue is also looked-up in the jndi tree
by the name of <dest-jndi-name>.

Does anybody have other ideas or see the need for using additional
properties like delivermode, priority etc..?

Best,

Ronald