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

[David Lloyd (JIRA)]

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

David Lloyd commented on WFLY-3670:
-----------------------------------

Oh, well in that case, I'd say you're simply doing it wrong: the shared stuff should not be in a module at all, just in a filesystem JAR.  Then, you add the filesystem JAR in to each deployment as a resource root.

> 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)