[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
I have tried all the combinations of Dependencies and Class-Path mentioned trying to get
common.jar to see com.test.module at run time. It sees it at deployment time. For some
reason a jar Manifested by an ejb-jar has run time classpath issues. I believe this is
related to the other ticket I submitted where a Manifested jar could not see javax.*
classes at run time. This is no doubt a class loader bug that only occurs to jars who
have been Manifested in by another jar.
Jar included in a MANIFEST.MF from an ejb jar can not see user
defined modules. Results in java.lang.ClassNotFound error.
--------------------------------------------------------------------------------------------------------------------------
Key: AS7-2566
URL:
https://issues.jboss.org/browse/AS7-2566
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.1.0.Alpha1
Environment: Windows 7 64 bit, 32bit Sun/Oracle JDK 1.6.0_27, Latest release of
JBoss 7.1.0.Alpha1 X.
Reporter: Rodney Kite
Assignee: David Lloyd
Priority: Blocker
Attachments: testJBossModuleErrorApp.zip
In an ear file user defined modules referenced from MANIFEST.MF are available to ejb jars
but not to the ejb jars manifested jars. When the jar manifested in tries to access a
modules classes a java.lang.ClassNotFoundException is raised. By the java jar spec the
manifested jar should be in classpath of the jar manifesting it. I tried putting the
modules Dependencies: reference in both the ejb jars MANIFEST.MF as well as the non ejb
jars MANIFEST.MF. This is a run time error it deploys fine.
--
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