[
https://issues.apache.org/activemq/browse/SMXCOMP-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated SMXCOMP-657:
---------------------------------
Attachment: SMXCOMP-657.patch
This patch also upgraded the camel version to 2.1-SNAPSHOT which has the patch
of [CAMEL-2068| https://issues.apache.org/activemq/browse/CAMEL-2068] for this
issue.
> Set the camelprocessor's thread context classloader with application context
> classloader
> ----------------------------------------------------------------------------------------
>
> Key: SMXCOMP-657
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-657
> Project: ServiceMix Components
> Issue Type: Improvement
> Components: servicemix-camel
> Reporter: Willem Jiang
> Fix For: servicemix-camel-2009.02
>
> Attachments: SMXCOMP-657.patch
>
>
> When Camel work within Servicemix4 , we will meet [the classloader
> issue|http://fusesource.com/issues/browse/MR-249].
> The better solution is when we call the camel processor we just set the
> thread context classloader with the application context classloader, and
> reset the classloader when the camel processor finishes it work. In this way,
> user can leverage the OSGi bundles imports package to manage the classloader
> issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
