On 03/03/2008, jgunz <[EMAIL PROTECTED]> wrote: > > Thanks James, I appreciate the help. > > If temporary destination URLs are going to be supported, will the ability to > create a temporary destination also be supported (either explicitly or in > the url somehow)
Yes! > -- otherwise you can only use camel on one end of a > communication over a temporary destination without dropping down to the raw > JMS api. > > Perhaps 2 different url syntaxes could be used, 1 for creating a new temp > dest and another for using an already created one: > > jms:newTempQueue > jms:tempQueue:<name> I was assuming that jms:tempQueue:<name> would lazily create a new temporary queue if a temporary queue is not registered by that name. We could then add some way to set the temporary destination manually if required if you wanted to reuse an existing temporary destination. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
