[jboss-jira] [JBoss JIRA] (WFLY-3670) Flag modules to be loaded in a distinct classloader context

[Wolf-Dieter Fink (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989919#comment-12989919 ] 

Wolf-Dieter Fink commented on WFLY-3670:
----------------------------------------

I did not meant to have absolute path for resources here.

The issue is that if a module is referenced from different applications the module itself is loaded with a unique classloader.
So all applications which depends on this module are using the same instance of static members.

In case of having a module implementation with such static objects and the application need to have these objects unique for each application the only approach at the moment is to copy the module.

The request is to have a flag like "separateClassLoaderPerDependency"
- at module.xml level to have a copy for all dependency references
- in the application (jboss-deployment-structure or MANIFEST) to have a separate in-memory copy for this application

> Flag modules to be loaded in a distinct classloader context
> -----------------------------------------------------------
>
>                 Key: WFLY-3670
>                 URL: https://issues.jboss.org/browse/WFLY-3670
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Wolf-Dieter Fink
>            Assignee: Jason Greene
>
> For some use-cases it will be helpful to have a module in a separate classloader (as copy) if it is used from different applications.
> An example is if the module includes classes which follow the singleton pattern but the singleton should be per application instead of instance wide.
> There are two possiblities to flag that
> - within the module.xml
> - within the module reference MAIFEST or jboss-deployment-structure.xml



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)