[
https://issues.jboss.org/browse/WFLY-3670?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-3670:
-----------------------------------
What is really being asked here is one of two things:
* Allow absolute paths for resource roots in jboss-deployment-structure.xml
* Allow a new kind of class path reference wherein the classes are duplicated rather than
referenced
Other application servers work in this mode (copying classes for each deployment), so it
is an aid to migration to be able to use the same behavior, even if it is very suboptimal
in other respects.
That said I think the first solution is the simplest.
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)