[jboss-jira] [JBoss JIRA] (WFLY-1428) Extra resource root added to WARs

[Radim Hatlapatka (JIRA)]

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

Radim Hatlapatka edited comment on WFLY-1428 at 5/31/13 3:52 AM:
-----------------------------------------------------------------

If I use:
{code}
classLoader.getResource(....);
{code}
I am able to get only the resources in META-INF directory.

If I use new feature for listing deployment resources:
{code}
Iterator<Resource> it = classLoader.iterateResources("/", true);
{code}
Between the listed resources are even resources in the root of archive and also resources in WEB-INF and also resources of the nested JAR files.


I have used the same classLoader for both cases. From my point of view it seems as some issue in iterateResources
                
      was (Author: rhatlapa):
    If I use:
{code}
classLoader.getResource(....);
{code}
I am able to get only the resources in META-INF directory.

If I use new feature for listing deployment resources:
{code}
Iterator<Resource> it = classLoader.iterateResources("/", true);
{code}
Between the listed resources are even resources in the root of archive and also resources in WEB-INF and also resources of the nested JAR files.

                  
> Extra resource root added to WARs
> ---------------------------------
>
>                 Key: WFLY-1428
>                 URL: https://issues.jboss.org/browse/WFLY-1428
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (JBoss Web), Web (Undertow)
>            Reporter: David Lloyd
>            Assignee: Remy Maucherat
>             Fix For: 8.0.0.Alpha2
>
>
> When the class path for WAR deployments is being assembled, it appears that the WAR's root is being added as a resource root.  This seems to be counter to spec; by default this should not be done.  Now that we have the ability to iterate class loader resources, this causes unusual things to be listed.
> Some users may desire this non-standard behavior though.  So, we should have a way (preferably simpler than {{jboss-deployment-structure.xml}}) to enable it; however in this case, the following paths *must* be excluded:
> * {{WEB-INF/lib}}
> * {{WEB-INF/classes}}
> * Any additional configured library or class directories
> * Any other nested, mounted JAR files

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