[jboss-jira] [JBoss JIRA] (AS7-5160) Support for static resources from /META-INF/resources from JBoss Module

[David Lloyd (JIRA)]

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

David Lloyd commented on AS7-5160:
----------------------------------

I am not sure how JBoss Web locates resources, but your above filter won't work; you probably want this instead:

{code:xml}
<imports>
  <include path="META-INF/resources"/>
  <include path="META-INF/resources/**"/>
</imports>
{code}

Notice the {{/}} before the {{**}}.  If JBoss Web is indeed using the class loader to load these resources, then this will do it.
                
> Support for static resources from /META-INF/resources from JBoss Module
> -----------------------------------------------------------------------
>
>                 Key: AS7-5160
>                 URL: https://issues.jboss.org/browse/AS7-5160
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Class Loading
>    Affects Versions: 7.1.1.Final
>            Reporter: Kirk Rasmussen
>            Assignee: David Lloyd
>
> It would be a nice extension to support loading Servlet 3.0 style fragements for static resources from JBoss modules. For example, for sharing static resources from Vaadin with multiple WAR files (2MB of static files) could be avoided:
> {code:xml}
> <jboss-deployment-structure>
>   <deployment>
>     <dependencies>
>       <module name="vaadin.static">
>         <imports>
>           <include path="META-INF**" />
>         </imports>            
>       </module>
>     </dependencies>
>   </deployment>
> </jboss-deployment-structure>
> {code}
> The module above would contain web static resources in /META-INF/resources/. This doesn't currently work unfortunately. When the JAR contained in the Module is embedded in the WAR file it works fine.

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