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:
- Any additional configured library or class directories
- Any other nested, mounted JAR files