> I am not suggesting that it creating queues duing Consumer construction is > what the API says it should do, as it is pretty clear that it only covers > creation creation of temporary queues, and (in our implementation of topic > subscriptions) creation and removal of the backing queues used for > DurableSubscriptions. >
Yes. The specification does not explicitly say when you should create a queue. But you always need a producer/consumer/browser/receiver in order to make use of a queue. Therefore I do not see anything wrong with creating a queue physically in the broker at the point of creating one of these objects that is associated with the queue. > The durability of the queues it is already creating by default is the point > of interest here though, not whether it should actually be creating them. > +1 > Message persistence is the only option given to users of the JMS API and is > persistent by default, so I dont see that as being open to interpretation. > The default client behaviour should allow for the delivery mode setting to > actually have an effect. The explicit choice is there to use non > persistent. > +1. I think whether to "actually persist a durable queue" or not is something that should be decided based on the message store you use. On the other hand as I have mentioned in my initial mail it creates durable queues by default if you use JNDI to get queue object instances. Thanks, Danushka
