Hello. I think I have found a solution to workaround this problem. As the main goal of the bean that need the service reference is to take control of the camel context (Lifecycle Strategy), it can deactivate all the camel contexts that belong to the given blueprint if it is aware of the availability of the service. For that, I've added a reference listener on the bean declaration, and two methods to take into account the service when it's bound or unbound.
Something like that : Perhaps this solution also will also help others with the same problem... Thanks for your answer. Regards -- View this message in context: http://servicemix.396122.n5.nabble.com/Blueprint-service-references-and-bundle-lifecycle-tp5721899p5721913.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
