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

David Lloyd (JIRA) jira-events at lists.jboss.org
Thu Jul 19 16:52:07 EDT 2012


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

David Lloyd commented on AS7-1928:
----------------------------------

If you want access to the META-INF of a dependency, you have to add the filter to allow META-INF *to that dependency*, not just to the resource (a module always exports all of its local resources including META-INF).
                
> 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: jboss-access-meta-inf.zip, 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

        


More information about the jboss-jira mailing list