[jboss-jira] [JBoss JIRA] (AS7-1928) Allow deployments to get access to the META-INF folder of their dependency module

[John Wu (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700529#comment-12700529 ] 

John Wu edited comment on AS7-1928 at 6/11/12 1:35 PM:
-------------------------------------------------------

Resources in META-INF dir of a dependency module is still somehow not accessible.

Here is the scenario:
1. I have a framework jar (modular-app-framework-1.0.0.jar) which has the following content:
{code}
/META-INF
|   /spring
|   |   +service-config.xml // defines serviceBeanInMetaInf
|   |   +web-config.xml     // defines webBeanInMetaInf
/spring
|   +service-config.xml // defines serviceBeanOutsideMetaInf
|   +web-config.xml     // defines webBeanOutsideMetaInf
+logback.xml
{code}
2. The framework jar is defined as a module as follows:
{code:xml}
// FILE: $JBOSS_HOME/modules/org/wjh/experimental/modular/artifact/module.xml
    <module xmlns="urn:jboss:module:1.1" name="org.wjh.experimental.modular" slot="artifact">
        <resources>
            <resource-root path="modular-app-framework-1.0.0.jar" />
        </resources>
    </module>
{code}
. The file modular-app-framework-1.0.0.jar is located in $JBOSS_HOME/modules/org/wjh/experimental/modular/artifact/
3. A Spring based web app tries to load the context files at {code}classpath*:META-INF/spring/*-config.xml and classpath*:spring/*-config.xml{code}
4. The result: *the config files located outside of META-INF/ are loaded*.
5. Environment: JBoss AS 7.1.1.Final, Spring 3.0.6.RELEASE
6. Please see the attached project for further details.
                
      was (Author: phantom_john):
    Resources in META-INF dir of a dependency module is still somehow not accessible.

Here is the scenario:
1. I have a framework jar (modular-app-framework-1.0.0.jar) which has the following content:
{code}
/META-INF
|   /spring
|   |   +service-config.xml // defines serviceBeanInMetaInf
|   |   +web-config.xml     // defines webBeanInMetaInf
/spring
|   +service-config.xml // defines serviceBeanOutsideMetaInf
|   +web-config.xml     // defines webBeanOutsideMetaInf
+logback.xml
{code}
2. The framework jar is defined as a module as follows:
{code:xml}
// FILE: $JBOSS_HOME/modules/org/wjh/experimental/modular/artifact/module.xml
    <module xmlns="urn:jboss:module:1.1" name="org.wjh.experimental.modular" slot="artifact">
        <resources>
            <resource-root path="modular-app-framework-1.0.0.jar" />
        </resources>
    </module>
{code}
. The file modular-app-framework-1.0.0.jar is located in $JBOSS_HOME/modules/org/wjh/experimental/modular/artifact/
3. A Spring based web app tries to load the context files at classpath*:META-INF/spring/*-config.xml and classpath*:spring/service-config.xml.
   Only the ones outside of META-INF/ are found.
4. Environment: JBoss AS 7.1.1.Final, Spring 3.0.6.RELEASE
5. Please see the attached project for further details.

                  
> Allow deployments to get access to the META-INF folder of their dependency module
> ---------------------------------------------------------------------------------
>
>                 Key: AS7-1928
>                 URL: https://issues.jboss.org/browse/AS7-1928
>             Project: Application Server 7
>          Issue Type: Feature Request
>    Affects Versions: 7.1.0.Alpha1
>            Reporter: Marius Bogoevici
>            Assignee: Stuart Douglas
>             Fix For: 7.1.0.Final
>
>         Attachments: modular-app.META-INF.not.accessible.zip
>
>
> Currently there is absolutely no mechanism (outside of manipulating dependencies programmatically through a subsystem) for deployments to get access to some META-INF/xyz files from a module that they declare as a dependency, except are in META-INF/services. 
> This is a serious impediment when considering the installation of third party libraries as shared libraries (modules) in JBoss AS. Some frameworks may rely upon locating internal descriptors in META-INF, and if the libraries are installed as modules, the descriptors are not accessible to the framework. Essentially, there is no way of accessing resources under META-INF unless they are either services, or the library is packaged in the deployment.

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