[JBoss JIRA] (AS7-2566) Jar included in a MANIFEST.MF from an ejb jar can not see user defined modules. Results in java.lang.ClassNotFound error.
12:44 p.m.
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: EJB
Affects Versions: 7.1.0.Alpha1, 7.0.2.Final
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: Carlo de Wolf
Priority: Blocker
Fix For: No Release
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
1:06 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite updated AS7-2566:
-----------------------------
Attachment: testJBossModuleErrorApp.zip
Test program to demonstrate error.
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: EJB
Affects Versions: 7.0.2.Final, 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: Carlo de Wolf
Priority: Blocker
Fix For: No Release
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
2:47 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf updated AS7-2566:
-------------------------------
Assignee: David Lloyd (was: Carlo de Wolf)
Fix Version/s: (was: No Release)
Affects Version/s: (was: 7.0.2.Final)
Priority: Major (was: Blocker)
Component/s: EE
(was: EJB)
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
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
5:09 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2566:
----------------------------------
Modular dependencies are not transitive, by default. By spec only class-path references
are transitively visible. If you want to make the dependencies visible transitively, you
have to add the "export" flag to the dependency declaration.
Example:
{noformat}
Dependency: org.foo.themodule export
{noformat}
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
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
5:11 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
David Lloyd resolved AS7-2566.
------------------------------
Resolution: Rejected
Usage question, not a bug.
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
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
1:03 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
I have tried every combination of including modules with export and it does not work.
Dependencies: com.test.module export, org.apache.log4j
for the MANIFEST.MF in the ejb jar and
Dependencies: com.test.module, org.apache.log4j
in the manifested jar file seems to be the correct combination.
I still get java.lang.NoClassDefFoundError for TestModule.java
This needs to work in order to run applications in JBoss 7 that would work in JBoss
4.2.x. There is no work around for this.
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
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
1:12 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
Tried putting Dependencies: com.test.module export in ears top MANIFEST.MF as well and it
does not work here either.
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
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
1:14 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite reopened AS7-2566:
------------------------------
Using export in the Dependencies does not resolve the issue. Configurations that deployed
in other releases of JBoss will not work in JBoss 7. There is no work around for
applications needing to export modules to manifested jar files. This is specifically a
run time error. It seems to have the correct visibility during deployment.
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
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
1:16 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite updated AS7-2566:
-----------------------------
Priority: Blocker (was: Major)
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
3:52 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2566:
----------------------------------
Because I'm not quite sure what you mean with some of your terminology, I'm going
to try and rephrase this issue.
"A JAR which is located within the ear/lib directory of the EAR does not have
visibility to a JAR which is referenced in the EAR's Manifest Class-Path".
Is this what you're saying?
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
4:10 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
No, It may work if jar is included in the lib directory but have not tried it.
A jar file included/referenced by a ejb-jar using a MANIFEST.MF entry does have run time
visibility to modules even if the module is exported.
(ejb.jar has MANIFEST.MF entry "Class-Path: common.jar" and
"Dependencies: com.test.module export")
testEar.ear
ejb.jar
common.jar
At run time if common.jar tries to use or create a object/class defined in com.test.module
a java.lang.ClassNotFoundException is raised.
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
4:36 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2566:
----------------------------------
Okay, I think I see. You should be able to see classes in {{com.test.module}} from
{{common.jar}} if any of the following are true:
# {{common.jar}}'s manifest contains {{Dependency: com.test.module}}
# {{common.jar}}'s manifest contains {{Class-Path: ejb.jar}} *and* {{ejb.jar}}'s
manifest contains {{Dependency: com.test.module export}}
# {{testEar.ear}}'s manifest contains {{Dependency: com.test.module export}}
Otherwise there's nothing which would cause this dependency to become visible. The
{{ejb.jar}} module doesn't "own" {{common.jar}}, so it cannot force its
dependencies onto it. On the contrary the {{ejb.jar}} module *depends* on {{common.jar}}
(that is to say, the arrow goes in the other direction). In other words if you reference
a JAR by class-path, you can "see" that JAR but it can't necessarily
"see" you unless it references you back again.
Does this help to explain things?
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
8:28 a.m.
[
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
6:40 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-2566:
----------------------------------
By "Manifested" do you mean "included via Class-Path"?
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
6:42 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas reassigned AS7-2566:
-----------------------------------
Assignee: Stuart Douglas (was: David Lloyd)
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: Stuart Douglas
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
9:58 a.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
Yes Manifested means in the MANIFEST.MF there is a reference to the jar in the
Class-Page entry of the ejb 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: Stuart Douglas
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
5:03 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-2566.
---------------------------------
Fix Version/s: 7.1.0.CR1
Resolution: Done
Verified that the attached application works. This was resolved by the class loading
changes I made recently.
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: Stuart Douglas
Priority: Blocker
Fix For: 7.1.0.CR1
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
5:10 p.m.
[
https://issues.jboss.org/browse/AS7-2566?page=com.atlassian.jira.plugin.s...
]
Rodney Kite commented on AS7-2566:
----------------------------------
Excellent!!! Thanks!!!!
Downloaded the latest release at 11:00am this morning tested and it worked.
Thanks Again!!!
Now trying to migrate our application.
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: Stuart Douglas
Priority: Blocker
Fix For: 7.1.0.CR1
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
4672
days inactive
4712
days old
17 comments
9 participants
participants (9)
-
Carlo de Wolf (Updated) (JIRA) -
David Lloyd (Commented) (JIRA)
-
David Lloyd (Resolved) (JIRA)
-
Rodney Kite (Commented) (JIRA)
-
Rodney Kite (Created) (JIRA)
-
Rodney Kite (Reopened) (JIRA)
-
Rodney Kite (Updated) (JIRA)
-
Stuart Douglas (Assigned) (JIRA)
-
Stuart Douglas (Resolved) (JIRA)