[
https://issues.jboss.org/browse/WFLY-905?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved WFLY-905.
---------------------------------
Resolution: Out of Date
The algorithm that resolves these dependencies has also been re-done, and should now
handle this case.
We now also support an explicit notion of inter deployment dependencies in jboss-all.xml.
Dynamic deployment modules are not visible to other ears referencing
them
-------------------------------------------------------------------------
Key: WFLY-905
URL:
https://issues.jboss.org/browse/WFLY-905
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Class Loading
Environment: Windows 7 64 bit, Oracle Jdk 1.6.0 32 bit
Reporter: Rodney Kite
Assignee: David Lloyd
During deployment there is an ERROR.
Failed to start service jboss.module.service."deployment.Mef.ear".main
JBAS018759: Failed to load module: deployment.Mef.ear:main ...
Caused by: org.jboss.modules.ModuleNotFoundException:
deployment.MefBusiness.ear.mefCommon.jar:main
A deployment ear has a jar that references another deployment ears jar/module indicated
in the referencing jars "Dependencies:" section of its Manifest.MF. It seems
that dynamic deployment modules are not visible to other ears referencing them.
This works fine in JBoss 7.1.1
--
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