You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Babel <ch...@gmail.com> on 2012/11/20 11:30:48 UTC
camel in OSGi: custom component resolved or listen to
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.
Re: camel in OSGi: custom component resolved or listen to
Posted by Babel <ch...@gmail.com>.
Hello Christian
Of course, I did. If I was not clear enough, I would explain what I'm
worrying about:
Camel resolves components by resolving OSGi specific service. I suppose this
service is only resolved and not actively listen to and would like to know
why.
Thanks for your answer, I'll try to use Blueprint as much as I can, even if
I don't understand how it could solve my problem.
--
View this message in context: http://camel.465427.n5.nabble.com/camel-in-OSGi-custom-component-resolved-or-listen-to-tp5722996p5723148.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel in OSGi: custom component resolved or listen to
Posted by Christian Müller <ch...@gmail.com>.
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 <ch...@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.
>
--