Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-781

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

    XMLWordPrintable

Details

    • Feature Request
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Rejected
    • 1.1.0.Beta2
    • None
    • Weld SPI
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            sivakumart_jira Sivakumar Thyagarajan (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: