You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Christoph Läubrich (JIRA)" <ji...@apache.org> on 2012/08/13 17:30:38 UTC
[jira] [Commented] (CAMEL-4147) Add support for lightweight OSGi
deployment (without Spring, Blueprint, ...)
[ https://issues.apache.org/jira/browse/CAMEL-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433213#comment-13433213 ]
Christoph Läubrich commented on CAMEL-4147:
-------------------------------------------
You can archive this with OSGi-DS, the only thing that is needed is a component XML and an additional header.
This way your bundle/jar is not bound to any OSGi Specific interface, it has support for autamatic tracking of dependant services etc.
If you can supply an example what is needed to bootsrap the cmale contex I can provide you an example how using OSGi-DS with that.
> Add support for lightweight OSGi deployment (without Spring, Blueprint, ...)
> ----------------------------------------------------------------------------
>
> Key: CAMEL-4147
> URL: https://issues.apache.org/jira/browse/CAMEL-4147
> Project: Camel
> Issue Type: New Feature
> Components: karaf, osgi
> Affects Versions: 2.7.2
> Reporter: Gert Vanthienen
> Fix For: Future
>
>
> We should be able to deploy Camel in a plain OSGi container without requiring Spring-DM or Blueprint to bootstrap the routes, cfr. http://camel.465427.n5.nabble.com/Camel-under-OSGi-without-Spring-et-al-td4507473.html
> A possible solution: add a ServiceTracker for RouteBuilder instances in the OSGi Service Registry and automatically create and start a CamelContext for any RouteBuilder instance it discovers.
> We should add a few optional properties that can be passed in when registering the service:
> * a CamelContext name, so the tracker can add multiple RouteBuilders to the same CamelContext
> * a property to disable automatically starting the context
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira