[
https://issues.apache.org/jira/browse/CAMEL-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054013#comment-13054013
]
Donald Whytock commented on CAMEL-4147:
---------------------------------------
A few issues I've experienced with this:
- OsgiDefaultCamelContext.start() should be sensitive to whether the services
it depends on are active. This seems to be at least one instance of
TypeConverter service.
- Similarly, it would be nice if routes were sensitive to whether the
components they need are active. This is reflected by instances of
ComponentResolver services.
- Named CamelContext-providing service instances, as suggested in the
description, would be a good way to provide CamelContext singletons across
bundles.
> 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: Improvement
> Affects Versions: 2.7.2
> Reporter: Gert Vanthienen
> Fix For: 2.9.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
