[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Steffen Wollscheid updated AS7-4253:
------------------------------------
Attachment: isolated-test-case.zip
Attached isolated-test-case.zip, which wraps the scenario into one project. The project
contains one Arquillian test case to demonstrate the problem.
To run the test just unzip, adapt the jbossHome property in
src/main/resource/arquillian.xml and run "mvn test".
The test assumes that the jboss is running as 127.0.0.1 with the native management
interace port 9999 (default).
Also the ejb remote calls are done without any credentials so remove the security-realm
attribute from the remoting-subsystem.
The test case contains four single tests, which all run using Arquillian @RunAsClient
- test -> osgiB -> ejb, tccl-unaware, which succeeds
- test -> osgiB -> ejb, tccl-awarem, which succeeds
- test -> osgiA -> osgiB -> ejb, tccl-aware, which succeeds
- test -> osgiA -> osgiB -> ejb, tccl-unaware, which fails
The calls from test to osgiX are done usig jmx. The call osgiA ot osgiB is an OSGi service
call.
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
Fix For: 7.2.0.Alpha1
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