[
https://issues.jboss.org/browse/WFLY-1388?page=com.atlassian.jira.plugin....
]
Thomas Diesler commented on WFLY-1388:
--------------------------------------
This doesn't replace system modules. The implementation uses a fallback when a module
cannot be loaded with the "deployment." prefix nor as a system module. It allows
for a user deployment to define a dependency without needing to know whether the
dependency is available as system module or got deployed with an alias. Again, system
modules are never shadowed.
Cannot load module alias defined for root deployment
----------------------------------------------------
Key: WFLY-1388
URL:
https://issues.jboss.org/browse/WFLY-1388
Project: WildFly
Issue Type: Bug
Components: Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 8.0.0.Alpha2
A module defined like this cannot get loaded by its module-alias
{code}
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
<deployment>
<resources>
<resource-root path="wrapped-resource.jar"
use-physical-code-source="true"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.jms.api"/>
<module name="org.apache.camel.core"/>
<module name="org.springframework.beans"/>
<module name="org.springframework.context"/>
<module name="org.springframework.core"/>
<module name="org.springframework.jms"/>
<module name="org.springframework.transaction"/>
<module name="org.slf4j"/>
</dependencies>
<module-alias name="org.apache.camel.component.jms"/>
</deployment>
</jboss-deployment-structure>
{code}
--
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