You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/04/16 16:43:58 UTC
[jira] [Commented] (CAMEL-8647) Make Camel OSGI Extender
Subsystem-Aware
[ https://issues.apache.org/jira/browse/CAMEL-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498093#comment-14498093 ]
ASF GitHub Bot commented on CAMEL-8647:
---------------------------------------
GitHub user manuelh9r opened a pull request:
https://github.com/apache/camel/pull/491
CAMEL-8647: Make Camel OSGI Extender Subsystem-Aware
Pull Request for https://issues.apache.org/jira/browse/CAMEL-8647
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manuelh9r/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/491.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #491
----
commit 139bd5de94b1a52e190d77b0801061a1d468d811
Author: Manuel Holzleitner <ma...@gmail.com>
Date: 2015-04-16T14:39:42Z
CAMEL-8647: Make Camel OSGI Extender Subsystem-Aware
----
> 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
> Reporter: Manuel Holzleitner
>
> 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-zNO9rEUXNOQ4ZH4Qw4FGseoR4zxqcTuQ@mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)