Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of dwhytock@gmail.com designates
 209.85.160.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=DSBIBTBC3IcKpS12r7KjV7dqc5Vw5n5Np8Lpg+ckZMf4BVyP8o3db1NeJXvFVRFDdA
         Z4Viz7N5G8psxlw7iM3T9CxQi90sWeUpiSUjpTa4lIm/ZuyQbcRpiCRo0yJx2ZnycyhJ
         p9t1tp8zaZzNrkfOpEri4labVPEeDpKHbsCUs=
MIME-Version: 1.0
In-Reply-To: <91783E5730D6DD4AB5B1B518437F54911A6196@de-ex013.groupinfra.com>
References: <BANLkTikfTxcXxJcs_xpgK2t0qU6e7MiQxQ@mail.gmail.com>
	<91783E5730D6DD4AB5B1B518437F54911A6196@de-ex013.groupinfra.com>
Date: Tue, 3 May 2011 18:26:21 -0400
Message-ID: <BANLkTimU9geSZ-hPYok=ahkHtPF0VC-TuA@mail.gmail.com>
Subject: Re: Problem designing a camel route for an OSGi system.
From: Donald Whytock <dwhytock@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I get multiple routes in OSGi by having a service that provides a
singleton CamelContext.  Bundles consume the same CamelContext and
create on it whatever routes they need.

Though I do this in Java, not Spring, so this might not be what you're
looking for.

Don

On Tue, May 3, 2011 at 5:18 PM, Klug, Johannes <johannes.klug@logica.com> w=
rote:
>
> I'm having some troubles with this as well. Could someone enlighten us wh=
at the best way would be to get multiple routes into a single OSGi applicat=
ion?
>
>
> -----Original Message-----
> From: Mark Doyle [mailto:markjohndoyle@googlemail.com]
> Sent: Sun 5/1/2011 10:02 PM
> To: users@camel.apache.org
> Subject: Problem designing a camel route for an OSGi system.
>
> I have the spring file below. It simply creates a couple of beans
> which are used in a camel route. The camel route is obviously
> configured in the context section. One of the beans is actually an
> OSGi service (id camelParameterProvider) which means it's used by
> multiple service consumer bundles (In this case there are many eclipse
> views using it to get data). Unfortunately this means all service
> consumers share the same bean which has the same route! (I assume the
> same camel context?) This would be fine but I want to filter the
> incoming data using the parameterFilterer bean. The filtering part
> works fine except that all the views are sharing the same service
> provider bean so when one filters the route all the other consumers
> only receive the filtered messages too.
>
> One way I explored to solve this was to use the bundle scope for the
> bean. Unfortunately the camel route references only a bean uri (the
> "to" part of the route) so no messages are routed. I guess camel has
> no way to know which instance of the bean to route to (and why would
> it).
>
> Is this a symptom of a bad design or is there a way around this.
> Perhaps creating a bean that provides the OGSi service AND is a
> routebuilder then trying to use that with bundle or prototype scope...
>
> P.S. I'm not sure if this is a Camel, Spring, or OSGi issue! =A0:)
>
> I created a diagram here that may explain the overall view better:
> http://dl.dropbox.com/u/10007025/hbird/pictures/hummingbird%20gui%20param=
eter%20retrieval.png
>
> Spring file:
>
> =A0 =A0 =A0 <!-- Acts as a dynamic filter -->
> =A0 =A0 =A0 <bean id=3D"parameterFilterer"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0class=3D"org.hbird.rcpgui.camelparameterpr=
ovider.ParameterNameFilterer">
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<!--
> =A0 =A0 =A0 =A0 Create a camel parameter provider bean for use by the ser=
vices-context.xml
> =A0 =A0 =A0 =A0 (Spring DM).
> =A0 =A0 =A0 =A0-->
> =A0 =A0 =A0 =A0<bean id=3D"camelParameterProvider"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0class=3D"org.hbird.rcpgui.camelparameterpr=
ovider.CamelParameterProvider"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0autowire=3D"autodetect">
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<!-- Create a jms endpoint for the route used by this prov=
ider -->
> =A0 =A0 =A0 =A0<bean id=3D"jms" class=3D"org.apache.camel.component.jms.J=
msComponent">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0snip!
> =A0 =A0 =A0 =A0</bean>
>
> =A0 =A0 =A0 =A0<camelContext id=3D"camelContextBean"
> xmlns=3D"http://camel.apache.org/schema/spring">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<route id=3D"fromJmsProcessedParametersOut=
" autoStartup=3D"false">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<from uri=3D"jms:topic:pro=
cessedParametersOut" />
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<camel:filter>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<camel:met=
hod bean=3D"parameterFilterer"></camel:method>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<to uri=3D=
"bean:camelParameterProvider?method=3DparameterIn" />
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</camel:filter>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</route>
> =A0 =A0 =A0 =A0</camelContext>
>
>
>
>
> Think green - keep it on the screen.
>
> This e-mail and any attachment is for authorised use by the intended reci=
pient(s) only. It may contain proprietary material, confidential informatio=
n and/or be subject to legal privilege. It should not be copied, disclosed =
to, retained or used by, any other party. If you are not an intended recipi=
ent then please promptly delete this e-mail and any attachment and all copi=
es and inform the sender. Thank you.
>
>