camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From enalposi <enalp...@yahoo.com>
Subject Re: Issue with JMS Temp Queues (Tibco EMS)
Date Mon, 14 Mar 2011 13:17:38 GMT
Hallo Christian - 

Right, we are using temp queues for responses, but need more control than
standard req/resp. The response may not just be synchronous but result in
several messages (this is not uncommon in the financial/analytics world and
in general helps creating dynamic interfaces that incrementally handle
results as they come in)

Installing dedicated queues or responses is not desirable, since we don't
want to manage multiple queues per service (would ultimately be 100s). Hence
we want to define one queue for incoming requests (which we multiplex on the
server and can then be dispatched to processing resources on a grid, etc)
and have dynamically created channels (i.e. not requiring to file change
tickets and comply with a tedious review and justification process)

To give the configuration of the routes is somehow difficult, as they are
dynamically created based on an internal framework that translates logical
destinations into actual routes. For outbound it goes something like this:

from(_from).setExchangePattern(_pattern).threads(_poolSize).process(_processor).to(_to).setId(_routeId)
_from in this case is a 'direct:' endpoint and _to a 'jms:' destination.
Sending is done with a ProducerTemplate.
_processor is one of our framework components that for example performs
custom serialization for x-platform.

Getting back to my problem In other words: Is it possible to use well
defined temp queues with straight Camel, or is it somehow abstracted away so
that a given temp Camel route may result in a random effective JMS endpoint?

Cheers!

--
View this message in context: http://camel.465427.n5.nabble.com/Issue-with-JMS-Temp-Queues-Tibco-EMS-tp3425694p3556262.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message