Re: Creating JMS temporary destinations

[jgunz <sl...@twcny.rr.com>]

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) -- 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>



James.Strachan wrote:
> 
> On 21/02/2008, jgunz <sl...@twcny.rr.com> wrote:
>>  I can't seem to find any documentation or examples that show how to
>> create a
>>  temporary queue/topic endpoint for ActiveMQ or JMS components. Is this
>>  supported?
> 
> We don't currently support the explicit creation of temporary
> destinations yet in camel-jms.
> 
> But I guess we could support some kind of syntax like...
> 
> jms:tempQueue:foo
> 
> which would refer to a named temporary queue (ditto for tempTopic).
> We'd just have to put a warning on the component that you cannot use
> CACHE_NONE cacheLevelName value for this to work; as otherwise the
> Connection would not be reused (which would mean it would be closed so
> that the temporary destination would become closed).
> 
> I've raised a JIRA to support this...
> https://issues.apache.org/activemq/browse/CAMEL-342
> 
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source Integration
> http://open.iona.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Creating-JMS-temporary-destinations-tp15620448s22882p15806051.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Creating JMS temporary destinations

[James Strachan <ja...@gmail.com>]

On 03/03/2008, jgunz <sl...@twcny.rr.com> 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