[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Carlo de Wolf updated AS7-2442: ------------------------------- Assignee: David Lloyd (was: Carlo de Wolf) Component/s: EE (was: EJB) -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Rodney Kite updated AS7-2442: ----------------------------- Workaround Description: There is no work around considering some want to deploy their application on other application servers by using the JEE standard with MANIFEST.MF files. Using static modules will work but restricts the developer to having to restart JBoss after compiles. (was: There is no work around considering some want to deploy their application on other application servers by using the JEE standard and MANIFEST.MF files. Using static modules will work but restricts the developer to having to restart JBoss after compiles.) Priority: Critical (was: Major) Description: When an ejb jar file in an ear references a regular non ejb jar file using the MANIFEST.MF Class-Path: entry the non ejb jar file has no visibility to javax.* classes. This results in the run time exception java.lang.NoClassDefFoundError when passing javax.* objects to the accessed jar or when constructing them in the jar. For example "java.lang.NoClassDefFoundError: javax/naming/InitialContext" is thrown when constructing a javax.naming.InitialContext in the accessed non ejb jar. Referencing jars through a MANIFEST.MF is standard J2EE and is defined in the JBOSS AS 7 Documentation as proper for portability. Using <ejb>/lib for the jar does not exhibit the error but prevents the jar from being used as a deployment module. Thus not a solution for a jar that needs to be shared across ears such as one which contains remote session bean interfaces. Adding javax.api to the Dependencies of the jars does not have any affect. (was: When an ejb jar file in an ear references a standard jar file from an MANIFEST.MF entry the standard jar file has no access to javax.* class. This results in a run time exception "java.lang.NoClassDefFoundError: javax/naming/InitialContext" when constructing a javax.naming.InitialContext or other javax.* class in the standard jar. Referencing jars through a MANIFEST.MF is defined in the JBOSS AS 7 Documentation as proper for portability. Using <ejb>/lib for the jar works but restricts access to the jar as a deployment module. ) -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Rodney Kite commented on AS7-2442: ---------------------------------- Also noticed that the jar referenced in MANIFEST.MF also does not have visibility to user defined modules. This is a little bit different than the javax.* error since it is a deployment time error and not a run time error. -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Adrian Everett edited comment on AS7-2442 at 11/2/11 3:31 PM: -------------------------------------------------------------- Without this fix, JBoss can't comply with basic Java standards. IMHO, elevating the ticket's status to Blocker wouldn't be a bad idea. was (Author: kidvid): If possible, I'd recommend this be elevated to be a blocker. Without this fix, JBoss can't fully comply with the standards. -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Rodney Kite edited comment on AS7-2442 at 11/2/11 3:50 PM: ----------------------------------------------------------- Elevated to Blocker. I simply can not migrate our application from previous JBoss versions to JBoss 7 with out this working. All jars included in MANIFEST.MF Class-Path: entry should be in the classpath of the jar including them as per the Java J2EE spec. Also as a side note the non ejb jar included in the MANIFEST.MF should be able to reference user defined JBoss modules through the Dependencies: entry in MANIFEST.MF. was (Author: rkite01): Elevated to Blocker. I simply can not migrate our application from previous JBoss versions to JBoss 7 with out this working. All jars included in MANIFEST.MF Class-Path: entry should be in the classpath of the jar including them as per the Java J2EE spec. Also as a side note the non jar included in the MANIFEST.MF should be able to reference user defined JBoss modules through the Dependencies: entry in MANIFEST.MF. -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-2442: ------------------------------ Fix Version/s: (was: No Release) Assignee: Stuart Douglas (was: David Lloyd) Thanks for finding this issue, we will fix it in 7.1 -- 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

[ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-2442. --------------------------------- Fix Version/s: 7.1.0.Beta1 Resolution: Done -- 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