[
https://issues.apache.org/jira/browse/SMXCOMP-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SMXCOMP-911.
-------------------------------------
Resolution: Fixed
Assignee: Gert Vanthienen
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1190042
> Add shared-library bundles to JBI component bundle classloader
> --------------------------------------------------------------
>
> Key: SMXCOMP-911
> URL: https://issues.apache.org/jira/browse/SMXCOMP-911
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-bean, servicemix-camel, servicemix-cxf-bc,
> servicemix-cxf-se, servicemix-drools, servicemix-eip, servicemix-exec,
> servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms,
> servicemix-ldap, servicemix-mail, servicemix-osworkflow, servicemix-quartz,
> servicemix-saxon, servicemix-scripting, servicemix-smpp, servicemix-snmp,
> servicemix-truezip, servicemix-validation, servicemix-vfs,
> servicemix-wsn2005, servicemix-xmpp
> Affects Versions: 2011.01
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 2011.02
>
>
> In a plain JBI scenario, every JBI component has the JBI shared library as
> its parent classloader. When we add the JBI components in ServiceMix 4,
> we're not using JBI packaging but we deploy them as OSGI bundles instead.
> Currently, these OSGi bundles only import the packages they need from the
> shared library bundles, but this sometimes causes problems when people move
> existing SAs from ServiceMix 3 to ServiceMix 4.
> If we add the shared-library bundles as {{Required-Bundle}}s to the JBI
> components, the classes available in the component would be a lot more
> similar than what we have in ServiceMix 3. Required-Bundle is not usually
> recommended in OSGi as it is too course-grained, but in this case there
> shouldn't be a real problem as we don't support multiple versions of the same
> JBI component anyway and the goal is to simulate the JBI classloader behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
