On Mon, Jul 9, 2012 at 4:49 PM, E.Gherardini <e.gherard...@hotmail.com> wrote: > Hello Claus, > I am getting problems in running this inside an OSGi context. > > In my opinion this should work registering the bean as a Service in the OSGi > context, from the same bundle which adds the route to the CamelContext, but > in such way when the BeanProcessor gets the message it cannot load the bean > implementing the RecipientList EIP. >
In the blueprint XML file, you need to have a <bean> for your bean, and refer to this bean id in the Camel route. And have the bean code in the same bundle. > Any suggestion ? > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-2-9-1-DeadLetterChannel-infinite-loop-tp5714961p5715743.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
