[
https://issues.jboss.org/browse/WFLY-1226?page=com.atlassian.jira.plugin....
]
Thomas Diesler resolved WFLY-1226.
----------------------------------
Resolution: Won't Fix
Won't Fix - OSGi is going to get removed
Populate repository with metadata from system modules/bundles
-------------------------------------------------------------
Key: WFLY-1226
URL:
https://issues.jboss.org/browse/WFLY-1226
Project: WildFly
Issue Type: Task
Components: OSGi, Server
Reporter: 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
For more information on JIRA, see:
http://www.atlassian.com/software/jira