[
https://issues.jboss.org/browse/AS7-3155?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas reassigned AS7-3155:
-----------------------------------
Assignee: Heiko Braun (was: Stuart Douglas)
This behaviour is not correct, global modules have no relationship to AS extensions.
If an extension is required to be added to the deployment then the extension generally
adds the dependency itself in a DUP.
The main point of global-modules is to allow the user to create shared modules that are
available to all deployments, so for example if you are deploying 10 spring apps to the
same server you could create a spring module and set it up as a global module, and then it
would be accessible to all deployed apps.
Console does not correctly edit the EE subsystems global-modules
----------------------------------------------------------------
Key: AS7-3155
URL:
https://issues.jboss.org/browse/AS7-3155
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Stuart Douglas
Assignee: Heiko Braun
Fix For: 7.1.0.Final
If you go to the EE subsystem in the console and try and add a global module the list
that pops up is limited to the modules that are provided by the as (i.e. only
org.jboss.as.* modules). As the primary use case for this feature is to allow users to
create their own system wide libraries, this is not very useful (there should never be any
need to add an org.jboss.as module as a global module).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira