Hi I have logged ticket https://issues.apache.org/jira/browse/CAMEL-5712
There is a bug in the camel-blueprint code that causes the BlueprintCamelContext to be started too soon. In the init() method the CamelContext was started. This causes a problem as there may be beans in the BlueprintContainer that refers to BlueprintCamelContext, which causes blueprint to call the init method when it lookup and IoC this reference. So I have changed the code to use a ServiceListener to listen for the even when the BlueprintContainer is done, as that happens when it registers itself in the service registry. Then this logic is also in line what camel-spring does, as we listen for the Spring Event ContextRefreshed. Which Spring emits when its done with all the namespace parsing and IoC stuff etc. I gave all the OSGi tests a run and they passed. As well gave a few examples in Karaf 2.2.9 a try as well. If any of the OSGi experts wanna take a look at the commit, then that would be lovely. http://svn.apache.org/viewvc?rev=1399808&view=rev -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
