Return-Path: 
 <users-return-40311-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D6458C7AF
	for <apmail-camel-users-archive@www.apache.org>;
 Wed, 19 Jun 2013 10:11:16 +0000 (UTC)
Received: (qmail 8723 invoked by uid 500); 19 Jun 2013 10:11:16 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 8462 invoked by uid 500); 19 Jun 2013 10:11:15 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 8451 invoked by uid 99); 19 Jun 2013 10:11:15 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jun 2013 10:11:15 +0000
X-ASF-Spam-Status: No, hits=2.8 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.219.53 as permitted sender)
Received: from [209.85.219.53] (HELO mail-oa0-f53.google.com) (209.85.219.53)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jun 2013 10:11:09 +0000
Received: by mail-oa0-f53.google.com with SMTP id k14so6219883oag.40
        for <users@camel.apache.org>; Wed, 19 Jun 2013 03:10:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=tH4yi0w2g7KniYFEbM1Q1gIbGtAQJSwBPPh+7tZw3zg=;
        b=vuYhojSRt8AdYiCwOxAtOWPirQ2q10ZR3GRtvwBP6N9Rb8eUx4XCBk36wYir7M9ES3
         ANpp8SaXMT0/4IIeh8OeB9Fb+1prRsCETkkKRstEk856mjSy5KV4iN9lbcrft8nScjLw
         TDP8foc4caWM+XWBLE0outor96OmgCSYAXenjDp/9h3IoV+BwNcRVmic1xdTxI9pfNID
         X85UJRFd5GE0ld3v75U4JvS6tzM9PZeNtlEfq4g2uxJoGhfjGX4xfnkPOLvdA0cfx02T
         uPl5xX6ly2t5B1HPIjuIMgjF043pvzaONFnaYz4xw3RSQ9GM8M/UJW9d58trlR4PtFuw
         l//w==
MIME-Version: 1.0
X-Received: by 10.60.80.233 with SMTP id u9mr1397335oex.132.1371636648513;
 Wed, 19 Jun 2013 03:10:48 -0700 (PDT)
Received: by 10.182.110.100 with HTTP; Wed, 19 Jun 2013 03:10:48 -0700 (PDT)
In-Reply-To: <1371631880036-5734346.post@n5.nabble.com>
References: <1371547134689-5734283.post@n5.nabble.com>
	<1371631880036-5734346.post@n5.nabble.com>
Date: Wed, 19 Jun 2013 12:10:48 +0200
Message-ID: 
 <CALvzYd8OzqPzSMVXJQJRNDpipR0BTsXkO5EcXptLUG-RK=bg9w@mail.gmail.com>
Subject: Re: Camel Integration Advice Needed
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=089e013cc5563217f404df7f0b18
X-Virus-Checked: Checked by ClamAV on apache.org

--089e013cc5563217f404df7f0b18
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

May be this link is useful for you [1].

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

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=3D"amqp:topic:FOO" />
<to uri=3D"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...

[1] http://www.slideshare.net/muellerc/apachecon-eu-2012

Best,

Christian M=FCller
-----------------

Software Integration Specialist

Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html

https://www.linkedin.com/pub/christian-mueller/11/551/642


On Wed, Jun 19, 2013 at 10:51 AM, jpbarto <Jason.P.Barto@gmail.com> wrote:

> Current Thinking
>
> After further research it is still not immediately evident to me on the E=
IP
> 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 topi=
cs
> 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 provider=
s
> dynamic and intelligent?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Integration-Advice-Needed-tp57342=
83p5734346.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--089e013cc5563217f404df7f0b18--