activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ilango_g <>
Subject Re: how to implement Content-based router
Date Wed, 15 Oct 2008 00:45:26 GMT

I would definitely want to try this one out. The other question I have is: is
it possible to have an MDB or a servlet do the same job? 

If it is, where can I start?
Meanwhile, I will start working on the content based router based on your


bsnyder wrote:
> On Mon, Oct 13, 2008 at 4:52 PM, ilango_g <> wrote:
>> Actually I have refined my question further:
>> There would be a queue that has messages
>> sitting on it. This queue has a listener that listens for messages, picks
>> up
>> a certain message (FIFO perhaps), and sends it off to a different queue
>> (channel) based on some information in a header field that identifies the
>> destination queue the message is intended for. For now, I assume that I
>> have
>> one message in my source queue that is meant to be delivered to one of
>> three
>> queues, Q1, Q2, Q3, based on the information in the JMS header of the
>> message.
>> If a sample is available that would be great to start off.
> As I said, creating a content-based router using Apache Camel is the
> easiest way to achieve this task. Take a look at the default
> configuration for ActiveMQ in conf/activemq.xml and you'll see a very
> basic example of configuring a route using Camel to route messages
> from a queue named example.A to a queue named example.B. You can
> easily augment this simple example to add the necessary configuration
> to implement the content-based router as shown on the Camel page
> ( under the
> heading 'Using the Spring XML Extensions'. Bear in mind that that is
> just one example as use of XPath is not required as Camel supports
> many different languages for use of expressions
> (
>  Bruce
> -- 
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
> Apache ActiveMQ -
> Apache Camel -
> Apache ServiceMix -
> Blog:

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message