[weld-issues] [JBoss JIRA] Created: (WELD-781) Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications

[Sivakumar Thyagarajan (JIRA)]

Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications
---------------------------------------------------------------------------------------------------------------------------------------------

                 Key: WELD-781
                 URL: https://jira.jboss.org/browse/WELD-781
             Project: Weld
          Issue Type: Feature Request
          Components: Weld SPI
    Affects Versions: 1.1.0.Beta2
            Reporter: Sivakumar Thyagarajan
            Priority: Minor


Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications.
In the current SPI loadClass(String name) is called and the container such as GlassFish, has no choice but to use the TCL or a generic classloader for the application. 

For applications that have multiple modules(such as an EAR), the container needs a mechanism to identify which module the Class/resource being loaded belongs to, so that it can use the appropriate module classloader.

So, for instance, it would be nice if the SPI could be modified to have a 
public Class<?> classForName(String name, BeanDeploymentArchive originatingBDA);  instead of classForName(name)
and equivalents for the other methods in ResourceLoader.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira