[
https://issues.apache.org/jira/browse/TUSCANY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584481#action_12584481
]
Jean-Sebastien Delfino commented on TUSCANY-2182:
-------------------------------------------------
I have fixed the classloader issues and committed the fix to trunk under SVN
revision r643814 but need to to more testing before porting the fix to the 1.2
branch.
In particular I'm seeing issues with ServletFilters on WebSphere App Server
6.1. The call to FilterChain.doFilter() in the Tuscany servlet filter seems to
return before the target application servlet is invoked, so the classloader set
on the thread context by the filter gets reset before the application code
executes (and that code then executes with an incorrect class loading context).
I'm investigating... and will update here as soon as I understand what's going
on with these servlet filters.
> ClassLoader issues with node2 launcher on WebSphere
> ---------------------------------------------------
>
> Key: TUSCANY-2182
> URL: https://issues.apache.org/jira/browse/TUSCANY-2182
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.2
> Reporter: Jean-Sebastien Delfino
> Assignee: Jean-Sebastien Delfino
> Fix For: Java-SCA-1.2
>
>
> The classloader used by Node2 uses a parent-first loading scheme which does
> not work on WebSphere application server, as different versions of the
> Tuscany runtime dependencies are on the classpath of Webapps in the WebSphere
> environment.
> The fix for that issue is simply to ensure that the Node2 launcher uses a
> parent-last classloading scheme to load its runtime classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
