Creating named durable queues using amq.topic is not allowed.

[Rajith Attapattu <ra...@gmail.com>]

Hi All,

During testing I noticed that if I define the following destination in
the jndi.properties file it will throw an error asking for a clientid
and a subscription to be defined.

destination.durableTopic =
topic://amq.topic//testTopicD?durable='true'&autodelete='true'

This check is enforced in the BindingURLParser.

If I add those properties as follows.
destination.durableTopic =
topic://amq.topic//testTopicD?durable='true'&autodelete='true'&clientid='test'&subscription='testQueueD'

Then the queue is set to clientid:subscription, and the queue name
defined in the URL is ignored.(Currently there is bug in that code as
well - see QPID-1875).

However I am not sure if forcing a particular pattern for the queue
name and treating it as a durable subscription if the exchange is
amq.topic and queue is durable is correct. This will create confusion
as when they tried to work with this queue using mgt-tools or connect
with other non java clients, it may not be obvious that the queue name
was generated in this case.

The users should have the freedom to define a queue name of their
choice. There is a clear path to create durable subscriptions in the
JMS API.
So I don't think we need to force it in the jndi.properties format.

What do you guys think?

Regards,

Rajith

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org