[jboss-jira] [JBoss JIRA] (AS7-2442) Non ejb jars referenced from an ejb jar in an ear via META-INF/MANIFEST.MF have no visiblity to javax.* classes

[Carlo de Wolf (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf updated AS7-2442:
-------------------------------

       Assignee: David Lloyd  (was: Carlo de Wolf)
    Component/s: EE
                     (was: EJB)

    
> Non ejb jars referenced from an ejb jar in an ear via META-INF/MANIFEST.MF have no visiblity to javax.* classes
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-2442
>                 URL: https://issues.jboss.org/browse/AS7-2442
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EE
>    Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
>         Environment: Windows 7 64 bit,  Sun/Oracle 32 bit JDK 1.6.0_27-b07,  Intel Core 2 Quad
>            Reporter: Rodney Kite
>            Assignee: David Lloyd
>             Fix For: No Release
>
>
> 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