camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: Camel Integration Advice Needed
Date Wed, 19 Jun 2013 10:10:48 GMT
May be this link is useful for you [1].

I would define a route which does the processing like this:
<from uri="direct:start" />
<to uri="..." />
<to uri="..." />

And in your route manager (or wherever), you can add routes at runtime
which are listening on AMQP endpoints and sending the exchanges to your
existing route:
<from uri="amqp:topic:FOO" />
<to uri="direct:start" />

Of course, you have to code this in Java (have a look into the slides to
get an idea how you can do this). Hope this helps...



Christian Müller

Software Integration Specialist

Apache Camel committer:
V.P. Apache Camel:
Apache Member:

On Wed, Jun 19, 2013 at 10:51 AM, jpbarto <> wrote:

> Current Thinking
> After further research it is still not immediately evident to me on the EIP
> which applies but to reiterate here is the functionality I seek,
> potentially
> multiple message providers publishing messages which, perhaps through a
> Dynamic Router, deliver messages to various endpoints based upon the topics
> to which the endpoints are subscribed.  My objective is to have the
> providers be intelligent so that they only subscribe to topics for which
> there are endpoint listeners.
> My current approach is to develop a 'route manager' that will instantiate
> provider endpoints in response to consumer subscriptions.  The 'route
> manager' would be configured with 'provider templates' so that
> theoretically
> any component could be configured for use in the Camel / Spring Context
> XML.
> The route manager would be a bean which is passed to my custom component
> that creates consumer endpoints.  When a consumer endpoint is created at
> run-time the route manager would instantiate provider endpoints for the
> consumer's topic if the provider endpoint does not already exist.  If the
> provider DOES already exist the consumer endpoint would be added to an
> existing route.  Am I misusing Camel by taking this approach?  How have
> others decoupled providers and consumers while still keeping the providers
> dynamic and intelligent?
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message