In the current implementation, the InjectionHandler.addJNDIDependency(InjectionContainer
container, String jndiName) needs to pass down the container.getClassLoader for use in the
lookup as the thread context class loader. I'm looking at validating this fixes the
current problem.
In terms of your example of multiple sources of a class, this has to be resolved based on
what the deployments import/export. The deployments that source X will have to declare the
class/version it exports. The deployment which consumes X will have an import statement
that is matched up to a source. In the absence of an import that more specifically matches
the A.jar export of X, the X found in the B.ear class loading domain should be resolved as
the matching source.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083072#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...