You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2008/03/27 17:11:32 UTC
[jira] Commented: (TUSCANY-2159) EJB binding extension not using
the correct EJB interface class loader
[ https://issues.apache.org/jira/browse/TUSCANY-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582709#action_12582709 ]
Jean-Sebastien Delfino commented on TUSCANY-2159:
-------------------------------------------------
Committed the short term fix in the trunk and 1.2 branch.
> EJB binding extension not using the correct EJB interface class loader
> ----------------------------------------------------------------------
>
> Key: TUSCANY-2159
> URL: https://issues.apache.org/jira/browse/TUSCANY-2159
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA EJB Binding Extension
> Affects Versions: Java-SCA-1.2
> Reporter: Jean-Sebastien Delfino
> Assignee: Jean-Sebastien Delfino
> Fix For: Java-SCA-1.2
>
>
> The EJB binding invoker seems to just rely on the classloader present on the current thread context to resolve EJB interface classes returned from a JNDI lookup of the EJB.
> This causes a ClassNotFoundException in the EJB interface specified on the reference is coming from another classloader than the current thread context classloader. This will likely cause similar issues with the EJB method parameter classes as well.
> A quick fix for release 1.2 is to set that classloader on the current thread context before calling the invoker's doInvoke method.
> A longer term fix will require more investigation.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org