[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-4253 at 7/18/12 3:42 AM:
--------------------------------------------------------------
Steffen says:
{quote}
I'm afraid the CNFE is precisely what the testcase was about in the first place.
The cascaded-accessor-bundle did not import the RemoteCalculator.class on purpose, because
it does not use it.
RemoteCalculator.class is a interface between the ejb-accessor-bundle (which imports it)
and the ebj-definition ear/jar - as such it is a implementation detail of the
ejb-accessor-bundle.
The CNFE arises from the fact that the TCCL is set to the HostBundleClassLoader of
cascaded-accessor-bundle when the ejb-accessor-bundle calls the ejb on behalf of the
cascaded-accessor-bundle.
{quote}
https://community.jboss.org/message/748378#748378
was (Author: thomas.diesler):
Steffen says:
{quote}
I'm afraid the CNFE is precisely what the testcase was about in the first place.
The cascaded-accessor-bundle did not import the RemoteCalculator.class on purpose, because
it does not use it.
RemoteCalculator.class is a interface between the ejb-accessor-bundle (which imports it)
and the ebj-definition ear/jar - as such it is a implementation detail of the
ejb-accessor-bundle.
The CNFE arises from the fact that the TCCL is set to the HostBundleClassLoader of
cascaded-accessor-bundle when the ejb-accessor-bundle calls the ejb on behalf of the
cascaded-accessor-bundle.
{quote}
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: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, 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