[jboss-jira] [JBoss JIRA] (AS7-2539) Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported

Abhi S (Updated) (JIRA) jira-events at lists.jboss.org
Mon Nov 7 18:16:45 EST 2011


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

Abhi S updated AS7-2539:
------------------------

    Description: 
According to the JEE 6 specification, section EE.8.2.1 (Bundled Libraries), Class-path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR could be used by the application developer to add these directories to the classpath of the sub-module.  However, this functionality has not yet been implemented in the JBoss AS7.1 (alpha-2 nightly build).

*Relevant JEE 6 spec, section EE.8.2.1, quotes:*
_Class-Path: list-of-jar-files-or-directories-separated-by-spaces_
_Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension._

The support for this functionality is *required* by the specification for the JBoss AS7.1 to be fully JEE 6 compliant.

*Side note:* This functionality is supported in JBoss 5.1, Weblogic, and WebSphere.


  was:
According to the JEE 6 specification, section EE.8.2.1 (Bundled Libraries), Class-path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR could be used by the application developer to add these directories to the classpath of the sub-module.  However, this functionality has not yet been implemented in the JBoss AS7.1 (alpha-2 nightly build).

*Relevant JEE 6 spec, section EE.8.2.1, quotes:*
_Class-Path: list-of-jar-files-or-directories-separated-by-spaces_
_Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension._

This support for this functionality is *required* by the specification for the JBoss AS7.1 to be fully JEE 6 compliant.

*Side note:* This functionality is supported in JBoss 5.1, Weblogic, and WebSphere.



    
> Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-2539
>                 URL: https://issues.jboss.org/browse/AS7-2539
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Deployment, Modules
>    Affects Versions: 7.1.0.Alpha1
>         Environment: Windows 7 64-bit
>            Reporter: Abhi S
>            Assignee: Thomas Diesler
>              Labels: classpath, deployment, ear
>         Attachments: jee-app.ear
>
>
> According to the JEE 6 specification, section EE.8.2.1 (Bundled Libraries), Class-path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR could be used by the application developer to add these directories to the classpath of the sub-module.  However, this functionality has not yet been implemented in the JBoss AS7.1 (alpha-2 nightly build).
> *Relevant JEE 6 spec, section EE.8.2.1, quotes:*
> _Class-Path: list-of-jar-files-or-directories-separated-by-spaces_
> _Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension._
> The support for this functionality is *required* by the specification for the JBoss AS7.1 to be fully JEE 6 compliant.
> *Side note:* This functionality is supported in JBoss 5.1, Weblogic, and WebSphere.

--
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

       



More information about the jboss-jira mailing list