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 johannes.klug@logica.com
 designates 213.199.154.206 as permitted sender)
Received-SPF: pass (mail5-am1: domain of logica.com designates 81.145.48.108
 as permitted sender) client-ip=81.145.48.108;
 envelope-from=johannes.klug@logica.com;
 helo=c1-ex001.groupinfra.com ;oupinfra.com ;
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01CC09D8.36A62BB4"
Subject: RE: Problem designing a camel route for an OSGi system.
Date: Tue, 3 May 2011 23:18:10 +0200
Message-ID: <91783E5730D6DD4AB5B1B518437F54911A6196@de-ex013.groupinfra.com>
Thread-Topic: Problem designing a camel route for an OSGi system.
thread-index: AcwIOtL3vDz7Ob4JR0iLB8nuUyxVfQBnMfja
References: <BANLkTikfTxcXxJcs_xpgK2t0qU6e7MiQxQ@mail.gmail.com>
From: "Klug, Johannes" <johannes.klug@logica.com>
To: <users@camel.apache.org>

------_=_NextPart_001_01CC09D8.36A62BB4
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I'm having some troubles with this as well. Could someone enlighten us what=
 the best way would be to get multiple routes into a single OSGi applicatio=
n?


-----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!  :)

I created a diagram here that may explain the overall view better:
http://dl.dropbox.com/u/10007025/hbird/pictures/hummingbird%20gui%20paramet=
er%20retrieval.png

Spring file:

       <!-- Acts as a dynamic filter -->
       <bean id=3D"parameterFilterer"
		class=3D"org.hbird.rcpgui.camelparameterprovider.ParameterNameFilterer">
	</bean>

	<!--
	 Create a camel parameter provider bean for use by the services-context.xm=
l
	 (Spring DM).
	-->
	<bean id=3D"camelParameterProvider"
		class=3D"org.hbird.rcpgui.camelparameterprovider.CamelParameterProvider"
		autowire=3D"autodetect">
	</bean>

	<!-- Create a jms endpoint for the route used by this provider -->
	<bean id=3D"jms" class=3D"org.apache.camel.component.jms.JmsComponent">
		snip!
	</bean>

	<camelContext id=3D"camelContextBean"
xmlns=3D"http://camel.apache.org/schema/spring">
		<route id=3D"fromJmsProcessedParametersOut" autoStartup=3D"false">
			<from uri=3D"jms:topic:processedParametersOut" />
			<camel:filter>
				<camel:method bean=3D"parameterFilterer"></camel:method>
				<to uri=3D"bean:camelParameterProvider?method=3DparameterIn" />
			</camel:filter>
		</route>
	</camelContext>


Think green - keep it on the screen.

This e-mail and any attachment is for authorised use by the intended recipi=
ent(s) only. It may contain proprietary material, confidential information =
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 recipien=
t then please promptly delete this e-mail and any attachment and all copies=
 and inform the sender. Thank you.


------_=_NextPart_001_01CC09D8.36A62BB4--