[
https://issues.apache.org/jira/browse/CAMEL-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550524#comment-14550524
]
Manuel Holzleitner edited comment on CAMEL-8647 at 5/19/15 2:27 PM:
--------------------------------------------------------------------
Hi Claus, could you check again?
I think this issue was unrelated to the subsystem changes and somewhere down
the road in the depending features in cxf-jaxrs and spring-context. For me at
least, it seems that this issue has been resolved behind the scenes:
{noformat}
.../apache-karaf-2.4.2/bin> ./karaf
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.4.2)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
karaf@root> features:chooseurl camel 2.16-SNAPSHOT
Adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.16-SNAPSHOT/xml/features
karaf@root> features:install camel
karaf@root> features:install camel-cxf
karaf@root>
{noformat}
was (Author: manuelh9r):
Hi Claus, could you check again?
I think this issue was unrelated to the subsystem changes and somewhere down
the road in the depending features in cxf-jaxrs and spring-context. For me at
least, it seems that this issue has been resolved behind the scenes:
{noformat}
.../apache-karaf-2.4.2/bin> ./karaf
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (2.4.2)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
karaf@root> features:install camel
Error executing command: No feature matching camel/0.0.0
karaf@root> features:chooseurl camel 2.16-SNAPSHOT
Adding feature url
mvn:org.apache.camel.karaf/apache-camel/2.16-SNAPSHOT/xml/features
karaf@root> features:install camel
karaf@root> features:install camel-cxf
karaf@root>
{noformat}
> Make Camel OSGI Extender Subsystem-Aware
> ----------------------------------------
>
> Key: CAMEL-8647
> URL: https://issues.apache.org/jira/browse/CAMEL-8647
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, osgi
> Reporter: Manuel Holzleitner
> Assignee: Christian Schneider
> Fix For: 2.16.0
>
>
> I would like to propose a change to the camel-core extender for components,
> type converters, etc. to allow to use camel-core with subsystem-aware
> OSGI-containers to separate components and it’s dependencies into subsystems.
> This would allow to isolate applications and camel components (incl. it’s
> libraries) from each other. I.e. you could run HTTP-related components that
> rely on (otherwise conflicting) HTTP client libs in different versions next
> to each other.
> Currently, the BundleTracker in the camel-core extender is initialized on its
> own BundleContext and therefore does not receive any events from started
> camel component bundles that reside in subsystems. I discussed a solution to
> make the camel extender subsystem-aware in the Aries mailinglist [1], who
> already conducted this change in the blueprint implementation.
> This approach from the upcoming R6 DS 1.3 spec was proposed by David Jencks
> as a solution:
> - use the system bundle (bundle 0) to look for events of interest, so you
> see them for all bundles
> - have the extender register an extender capability
> - have bundles that need extension register a matching extender requirement
> - the extender should only extend bundles with no extender requirement or
> ones with extender requirements wired to their own extender capability.
> I implemented this approach accordingly for camel and tested it in
> combination with the Aries subsystem module. Any feedback to this would be
> very much appreciated.
> [1]
> http://mail-archives.apache.org/mod_mbox/aries-user/201503.mbox/%3CCADE24oihG71CdC=pz-zno9reuxnoq4zh4qw4fgseor4zxqc...@mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
