[jboss-jira] [JBoss JIRA] (AS7-4615) Define a database of system modules
[
https://issues.jboss.org/browse/AS7-4615?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4615:
-------------------------------------
David says:
{quote}
Multiple module directories is not an app server feature; it's a feature of the
particular module loader implementation that we use by default. The app server has no
control over the topology of the modules; in fact it could be launched by a completely
alternative module loader that doesn't even use the file system.
If you need a database of system modules and their dependencies you'll have to
maintain that external to the module system because there is no contract there. The best
place to maintain this sort of module database would probably be within the OSGi
subsystem. There is currently no contract to enumerate the list of potentially loadable
modules from a module loader.
{quote}
Define a database of system modules
-----------------------------------
Key: AS7-4615
URL: https://issues.jboss.org/browse/AS7-4615
Project: Application Server 7
Issue Type: Task
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
The OSGi configuration supports ModuleIdentifiers. So for example
{code}
<capability name="javax.transaction.api"/>
{code}
references the JTA API module. This actually delegates to the repository implementations
which in turn delegates to the ModuleIdentityArtifactProvider.
If the AppServer supports the notion of multiple directories where modules can get loaded
from, the ServerEnvironment should reflect that properly. I cannot just load a module on
trial/error basis because we use the Repository for impact ananlysis. i.e. Find the
modules/bundles that provide the transitive set of capabilities for a given set of
requirements (without modifying the runtime).
--
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