[
https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s...
]
Marius Bogoevici commented on AS7-1928:
---------------------------------------
Well, we could always filter out well-known resources such as META-INF/MANIFEST.MF or
others, for example. The current behaviour is simply rendering existing JAR resources
invisible, without providing a way to render them visible on demand.
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
Priority: Critical
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira