camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1043) ResolverUtil - Refactor to allow easier extensions for OSGi resolutions for different OSGi platforms
Date Sat, 01 Nov 2008 20:35:05 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46955#action_46955
] 

Gert Vanthienen commented on CAMEL-1043:
----------------------------------------

I rather think we should try to leverage the OSGi registry more when using Camel on an OSGi
platform.  If we enhance our bundles and add a bundle activator to register their own converters
and components, we can avoid having to scan across bundles and running into this kind of OSGi
platform incompatibilities. 

Using this approach, we would also have a foundation for starting to react more dynamically
when bundles are added and removed from the platform.  We could e.g. start/stop routes as
bundles with components are started/stopped or (in the future) add some kind of interceptor
that can be started/stopped from a bundle.


> ResolverUtil - Refactor to allow easier extensions for OSGi resolutions for different
OSGi platforms
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1043
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1043
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Claus Ibsen
>             Fix For: 2.0.0
>
>
> ResolverUtil has some internal code that detects if the classloader(s) is OSGi aware
or not. ResolverUtil should expose strategy methods to allow us to create sub classes, or
inject resolvers that cater for this OSGi resolution.
> Maybe expose some public API for end-users to customize this at configuration time, so
they can let Camel run in any OSGi platform of choice.
> This is especially a problem with the dynamic type converters discoverer. That scans
all bundles.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message