[ 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1928: ---------------------------------- This should take two forms: # An additional flag option to the {{Dependencies:}} manifest item called {{meta-inf}} (case insensitive) which adds an accept filter for {{META-INF/**}} to the filter chain. # Ensuring that {{jboss-deployment-structure.xml}} supports either this flag or explicit filter specifications in any dependency sections it may provide. -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] Stuart Douglas reassigned AS7-1928: ----------------------------------- Assignee: Stuart Douglas -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu updated AS7-1928: ------------------------- Attachment: modular-app.META-INF.not.accessible.zip 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. -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1928: ---------------------------------- You have to define the dependency to include the a filter that includes META-INF (see my comment up above; you'll have to use jboss-deployment-structure.xml though in this case). Also do not specify the slot; it'll cause you trouble later. -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu commented on AS7-1928: ------------------------------ Resources in META-INF/ in a module resource (JAR file or expanded directory) are not accessible *from within that module*. Quote from the Issue Description: {quote} 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. {quote} Here is the scenario: # I have a framework jar (access-meta-inf-framework-1.0.0.jar) which has the following content: {code} /org/... // listener, servlet, and util classes /META-INF | +Resource.txt +NormalClasspathResource.txt {code} # The framework jar is defined as a module as follows: {code:xml} <module xmlns="urn:jboss:module:1.1" name="org.wjh.jboss.module.framework"> <resources> <resource-root path="access-meta-inf-framework-1.0.0.jar"> <filter> <include path="META-INF/**" /> </filter> </resource-root> </resources> <dependencies> <module name="javax.servlet.api" export="true" /> <module name="javax.api" export="true" /> </dependencies> </module> {code} The file access-meta-inf-framework-1.0.0.jar is located in $JBOSS_HOME/modules/org/wjh/jboss/module/framework/ # The result is: {code} ... ... ... === Initializing ServletContext. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Initializing Servlet. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Servicing HttpServletRequest. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt {code} # You may verify that with the attached project (jboss-access-meta-inf.zip), which is stemmed from a real issue discussed here (http://stackoverflow.com/questions/8098684/spring-module-in-jboss-7). -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu edited comment on AS7-1928 at 7/19/12 3:04 PM: ------------------------------------------------------- Resources in META-INF/ in a module resource (JAR file or expanded directory) are *still* not accessible *from within that module*. Quote from the Issue Description: {quote} 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. {quote} Here is the scenario: # I have a framework jar (access-meta-inf-framework-1.0.0.jar) which has the following content: {code} /org/... // listener, servlet, and util classes /META-INF | +Resource.txt +NormalClasspathResource.txt {code} # The framework jar is defined as a module as follows: {code:xml} <module xmlns="urn:jboss:module:1.1" name="org.wjh.jboss.module.framework"> <resources> <resource-root path="access-meta-inf-framework-1.0.0.jar"> <filter> <include path="META-INF/**" /> </filter> </resource-root> </resources> <dependencies> <module name="javax.servlet.api" export="true" /> <module name="javax.api" export="true" /> </dependencies> </module> {code} *The file access-meta-inf-framework-1.0.0.jar is located in $JBOSS_HOME/modules/org/wjh/jboss/module/framework/main/* # The jboss-deployment-structure.xml in the Access_META-INF.ear/META-INF/ {code:xml} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> <ear-subdeployments-isolated>true</ear-subdeployments-isolated> <deployment> <dependencies> <module name="org.wjh.jboss.module.framework" export="true" meta-inf="export" /> </dependencies> </deployment> </jboss-deployment-structure> {code} # The result is: {code} ... ... ... === Initializing ServletContext. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Initializing Servlet. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Servicing HttpServletRequest. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt {code} # You may verify that with the attached project (jboss-access-meta-inf.zip), which is stemmed from a real issue discussed here (http://stackoverflow.com/questions/8098684/spring-module-in-jboss-7). # The environment: JBoss AS 7.1.1.Final, Oracle JDK 1.6.0_31, Windows XP SP3. was (Author: phantom_john): Resources in META-INF/ in a module resource (JAR file or expanded directory) are *still* not accessible *from within that module*. Quote from the Issue Description: {quote} 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. {quote} Here is the scenario: # I have a framework jar (access-meta-inf-framework-1.0.0.jar) which has the following content: {code} /org/... // listener, servlet, and util classes /META-INF | +Resource.txt +NormalClasspathResource.txt {code} # The framework jar is defined as a module as follows: {code:xml} <module xmlns="urn:jboss:module:1.1" name="org.wjh.jboss.module.framework"> <resources> <resource-root path="access-meta-inf-framework-1.0.0.jar"> <filter> <include path="META-INF/**" /> </filter> </resource-root> </resources> <dependencies> <module name="javax.servlet.api" export="true" /> <module name="javax.api" export="true" /> </dependencies> </module> {code} *The file access-meta-inf-framework-1.0.0.jar is located in $JBOSS_HOME/modules/org/wjh/jboss/module/framework/main/* # The result is: {code} ... ... ... === Initializing ServletContext. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Initializing Servlet. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt ... ... ... === Servicing HttpServletRequest. ... ... ... The following resource(s) are found at location NormalClasspathResource.txt ... ... ... --- jar:file:$JBOSS_MODULEPATH/org/wjh/jboss/module/framework/main/access-meta-inf-framework-1.0.0.jar!/NormalClasspathResource.txt ... ... ... *** *** NO resource is found at location META-INF/Resource.txt {code} # You may verify that with the attached project (jboss-access-meta-inf.zip), which is stemmed from a real issue discussed here (http://stackoverflow.com/questions/8098684/spring-module-in-jboss-7). # The environment: JBoss AS 7.1.1.Final, Oracle JDK 1.6.0_31, Windows XP SP3 -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu commented on AS7-1928: ------------------------------ Hi David, I think you might misunderstand my intention. What I'm trying to do is to *access the resources in META-INF/ in a JAR (defined as a module) from a class in that same JAR*. I tried tweaking the module.xml and jboss-deployment-structure.xml in various ways but no luck. Did I miss anything? -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu commented on AS7-1928: ------------------------------ This is how get the class loader {code:java} Thread.currentThread().getContextClassLoader() {code} -- 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

[ https://issues.jboss.org/browse/AS7-1928?page=com.atlassian.jira.plugin.s... ] John Wu commented on AS7-1928: ------------------------------ This issue seems fall off the radar. Should I create a new issue and link it to this one, since this one is "Resolved". -- 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