Hi, Having both makes sense as some applications rely on an error when a queue is not present. ActiveMQ for exmaple creates queues server side on the fly when you use the session to create them client side and it can be a pain.
Not posted here for ages, will give the M2 build a spin when its out with Hermes. Regards, Colin. http://hermesjms.com > -----Original Message----- > From: Robert Greig [mailto:[EMAIL PROTECTED] > Sent: 12 April 2007 12:35 > To: [EMAIL PROTECTED] > Subject: Re: [java] [client] Automatic creation and binding > of JMS Queues with consumer in Java Client > > On 12/04/07, Martin Ritchie <[EMAIL PROTECTED]> wrote: > > > I've just recently be going over the fact that we automatically > > declare and bind queues when we create a new consumer. In a > real world > > system we wouldn't want to have client code automatically > > creating/binding JMS Queues. > > Well, we may not want to have that enabled by default but it > can be useful functionality. > > > I just wondered if any of my fellow qpid-ians would have a problem > > with this change in the java client until we re-layer and > remove this > > auto-creation code for queues completely. > > I think it's sensible that the default is that queues cannot > be created on the fly but we currently have at least one > application in production that relies on this behaviour so > any future solution must support this in some form. > > RG >
