[jboss-jira] [JBoss JIRA] (AS7-4253) TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules

Sun Mar 25 18:34:47 EDT 2012

     [ https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved AS7-4253.
---------------------------------

    Fix Version/s:     (was: 7.2.0.Alpha1)
       Resolution: Won't Fix

As far as I can see this is not a bug. The ejb: namespace is a client side namespace, it does no server lookups by design (except when looking up SFSB's). 

If you are attempting to lookup an EJB remote interface that the TCCL cannot load then there is simply no way for JNDI to magically figure out the correct class loader to use.

This is compounded by the fact that when using remote EJB's it is actually common to have the remote interfaces defined in several different deployments, so there are actually several different class loaders that are 'correct'. We need some mechanism to determine which one to use, and the standard way to do this in java is the TCCL. 

> TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules
> ------------------------------------------------------------------------------------------
>
>                 Key: AS7-4253
>                 URL: https://issues.jboss.org/browse/AS7-4253
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, OSGi
>            Reporter: Thomas Diesler
>            Assignee: jaikiran pai
>         Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip, isolated-test-case.zip
>
>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira