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

[ https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s... ] Steffen Wollscheid commented on AS7-4253: ----------------------------------------- @Stuart A few notes on your comment: A. It does not matter, how many deployments the interfaces are defined in -- all interfaces are imported into the calling bundle's classloader via osgi, so code in the bundle has every reason to expect the interface classes to be known, whenever it calls a method - and that is what happens in all cases, EXCEPT when the method called uses the TCCL as classloader. B. In an EJB application it is not uncommon for an application server to act as a remote EJB client. C. I do not expect magic from the JNDI, i expect it to work reliably. The current programming stops the TCCL from containing the classes, which are currently executed on that thread -- this is a BUG. Period. The bug lies not necessarily with JNDI - in the originial discussion i proposed some kind of interceptor updating the TCCL whenever a thread enters a bundle, perhaps using the class returned from BundleContext.getService(). It's up to you guys to find a solution for this bug -- for a bug it is, and it is not going to go away by closing this ticket. -- 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