You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2010/11/02 13:03:00 UTC
[jira] Created: (CAMEL-3302) OsgiPackageScanClassResolver should
have Non-OSGi classloader check fallback
OsgiPackageScanClassResolver should have Non-OSGi classloader check fallback
----------------------------------------------------------------------------
Key: CAMEL-3302
URL: https://issues.apache.org/activemq/browse/CAMEL-3302
Project: Apache Camel
Issue Type: Bug
Components: camel-spring
Affects Versions: 2.5.0
Reporter: Freeman Fang
Fix For: 2.6.0
This is necessary when use JBI packaging for servicemix-camel ServiceUnit so that we get chance to use SU classloader to scan packages in the ServiceUnit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-3302) OsgiPackageScanClassResolver should
have Non-OSGi classloader check fallback
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-3302.
---------------------------------
Resolution: Fixed
Applied the patch with thanks to Freeman, I also added an unit test to make sure the fallback is working.
> OsgiPackageScanClassResolver should have Non-OSGi classloader check fallback
> ----------------------------------------------------------------------------
>
> Key: CAMEL-3302
> URL: https://issues.apache.org/activemq/browse/CAMEL-3302
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 2.5.0
> Reporter: Freeman Fang
> Assignee: Willem Jiang
> Fix For: 2.6.0
>
> Attachments: CAMEL-3302.patch
>
>
> This is necessary when use JBI packaging for servicemix-camel ServiceUnit so that we get chance to use SU classloader to scan packages in the ServiceUnit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-3302) OsgiPackageScanClassResolver should
have Non-OSGi classloader check fallback
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-3302:
-----------------------------------
Assignee: Willem Jiang
> OsgiPackageScanClassResolver should have Non-OSGi classloader check fallback
> ----------------------------------------------------------------------------
>
> Key: CAMEL-3302
> URL: https://issues.apache.org/activemq/browse/CAMEL-3302
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 2.5.0
> Reporter: Freeman Fang
> Assignee: Willem Jiang
> Fix For: 2.6.0
>
> Attachments: CAMEL-3302.patch
>
>
> This is necessary when use JBI packaging for servicemix-camel ServiceUnit so that we get chance to use SU classloader to scan packages in the ServiceUnit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3302) OsgiPackageScanClassResolver should
have Non-OSGi classloader check fallback
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated CAMEL-3302:
--------------------------------
Attachment: CAMEL-3302.patch
append patch to fix this issue
> OsgiPackageScanClassResolver should have Non-OSGi classloader check fallback
> ----------------------------------------------------------------------------
>
> Key: CAMEL-3302
> URL: https://issues.apache.org/activemq/browse/CAMEL-3302
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 2.5.0
> Reporter: Freeman Fang
> Fix For: 2.6.0
>
> Attachments: CAMEL-3302.patch
>
>
> This is necessary when use JBI packaging for servicemix-camel ServiceUnit so that we get chance to use SU classloader to scan packages in the ServiceUnit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.