On Thu, Mar 3, 2011 at 12:50 PM, JacobS <[email protected]> wrote: > Hi, > > I did some debugging and apparently the beanholder for the bean processor > (of bean pojoSplitter ) has the wrong camelcontext. > I have 2 camelconetxts in my app one in each osgi bundle and for some > unknown reason camel has attached the wrong context to the bean. that is why > in 'CompositeRegistry' the lookup method does not find the bean ( it is > looking in the wrong applicationcontext ) >
So you have 2 bundles, and each bundle have 1 CamelContext in the XML file. Are the XML file in each bundle different? Or do they both define a <bean id="pojoSplitter"> and is this class in each bundle? Do you export the bean into the osgi service registry? Camel looks in OSGi service registry first, and then fallback to look into the Spring ApplicationContext (= the XML file) > Any idea how this could happen ? > No. > Jacob > > -- > View this message in context: > http://camel.465427.n5.nabble.com/split-with-spring-DSL-bean-tp3405576p3407810.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
