On Fri, 2011-04-29 at 06:40 -0700, mruan wrote: > Then it's will be very strange indeed that nobody needs to do what I am > supposed to do. Why do we have to create a queue in order to send a message > even if the queue exists already? > > I study the faq's carefully which Tim told me to do, but I am sorry that I > still don't find the solution. Put the problem in another way: > > I don't necessarily have to use asynchronous method, I use "receive" method > which is synchronous. First time I create a queue and I am able to send > messages to that queue, but second time because the queue is already there, > so I must not create it again, just send another messages to the existing > queue, but I don't know how, nobody? >
So are you asking why you have to call 'createQueue' on the client side? If I understand what you asking then calling the createQueue doesn't create a new one if there's already on there that matches the name you've given it, it just create the local representation of the queue object so that when you send a message or call receive the client code knows that you are producing or consuming on. If that's not it maybe you can express your intent with some code to make clear what you want the client to do. Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference
