[
https://issues.apache.org/jira/browse/CAMEL-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987511#comment-16987511
]
Claus Ibsen commented on CAMEL-14215:
-------------------------------------
Thanks for keep working on this.
Thanks so what I think is really taking people with some surprise is that it
registers Camel routes into the same single camel context from any bundles. The
point of Apache Karaf was to be like an app server where each bundle is
isolated. So this goes against this practice. This should be documented much
much more clearly. And also it lacks features with the ease of use how to
configure camel context itself (you end up with its defaults) and how would
people do dependency injections for beans etc.
Also it should be renamed to camel-osgi-activator, and moved to components (as
its not a core piece, eg not used by other osgi like osgi blueprint which is
the main osgi support in Camel).
> Camel Main for OSGi
> -------------------
>
> Key: CAMEL-14215
> URL: https://issues.apache.org/jira/browse/CAMEL-14215
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, camel-main
> Affects Versions: 3.x
> Reporter: Bob Paulin
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Labels: karaf, osgi
> Fix For: 3.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The current camel-core-osgi implementation sets up everything to work in an
> OSGi environment but does not start the OsgiDefaultCamelContext . Currently
> Spring Boot has an implementation that recognizes RouteBuilder components and
> adds them to the context at starter. This issue is to create a similar OSGi
> implementation that achieves the following goals:
>
> 1) Starts a CamelContext the is available to the entire runtime.
> 2) Detects and adds RouteBuilders that have been registered as services in
> the runtime prior to the Context Starting.
> 3) Detects and adds new RouteBuilders that are registered after the context
> is started.
> 4) Detects and removes RouteBuilders as they are de-registered from the
> runtime.
> 5) Allows the runtime to stop the CamelContext when the runtime or bundle is
> stopped.
>
>
> For discussion see
> [https://lists.apache.org/thread.html/63506b8fac49c9f50a921ba0fd81ed37e69c66ad778fb9d16adb90c3@%3Cdev.camel.apache.org%3E]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
