You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2009/10/19 08:27:53 UTC

[jira] Work started: (SMXCOMP-657) Set the camelprocessor's thread context classloader with application context classloader

     [ https://issues.apache.org/activemq/browse/SMXCOMP-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SMXCOMP-657 started by Gert Vanthienen.

> 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
>            Assignee: Gert Vanthienen
>             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.