[
https://issues.jboss.org/browse/AS7-5864?page=com.atlassian.jira.plugin.s...
]
John Wu commented on AS7-5864:
------------------------------
# Using the ClassLoader of my own class does give me the access to META-INF/blah.ext;
However,
# I encountered this issue when I try to put spring framework jars into a module. And
spring has a number of internal descriptors located in META-INF/. I believe other
libraries may also have other internal stuff located in META-INF/. This issue prevents
them from being installed as modules.
Classes of a module cannot get access to the META-INF folder in its
own jar/module
----------------------------------------------------------------------------------
Key: AS7-5864
URL:
https://issues.jboss.org/browse/AS7-5864
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Affects Versions: 7.1.1.Final
Reporter: John Wu
Assignee: David Lloyd
Attachments: jboss-access-meta-inf.zip
Currently there is absolutely no mechanism for classes of a module to get access to some
META-INF/xyz files in its own jar/module, 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 itself. 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 is the un-resolved part of issue
[
AS7-1928|https://issues.jboss.org/browse/AS7-1928].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira