Did you tried blueprint? It has possibilities to export/import services/beans to/from the OSGI registry and it makes your life much easier...
Best, Christian On Tue, Nov 20, 2012 at 11:30 AM, Babel <chpa...@gmail.com> wrote: > Hello dear all! > > After having search on Internet and also on the camel-osgi tutoroial, I'm > stil not sure about that point : > > As deploying my custom component in an OSGi bundle, I found the > ComponentResolver interface which I use to publish my own service to let > CamelContexts find my component. From some tests I've done in Karaf, I > think > CamelContext does only resolve the Component service but not listen to and > thus, the camel context does not react when the component bundle is > stopped. > is this the case? > > I suppose is really difficult to increase the osgi integration of Camel so > much the contexts and the route handle the component bundle lifecycle > modifications. > > Many thanks for any point about this. It's always a pleasure to use Camel > and also deploy it in OSGi! > > Best > > Christophe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-in-OSGi-custom-component-resolved-or-listen-to-tp5722996.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
