camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CAMEL-1043) ResolverUtil - Refactor to allow easier extensions for OSGi resolutions for different OSGi platforms
Date Sun, 04 Jan 2009 07:27:06 GMT

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

njiang edited comment on CAMEL-1043 at 1/3/09 11:25 PM:
--------------------------------------------------------------

Now there is an Activator in Camel-osig which takes care of the searching the META-INFO of
the camel components bundles for components , type converters and language.
In this way , other components will not do any additional work to be osgi friendly, and the
ResolverUtil's will not need to check the classloader for loading the bundles.

TODO  we need to refactor the ResolverUtil to pull the osgi relating codes into camel-osgi
module.

      was (Author: njiang):
    Now there is an Activator which takes care of the searching the META-INFO of the camel
components bundles for components and type converters.

TODO  we need to refactor the ResolverUtil to pull the osgi relating codes into camel-osgi
module.
  
> 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
>            Assignee: Willem Jiang
>             Fix For: 1.5.1, 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