[
https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin....
]
Remy Maucherat resolved JBWEB-279.
----------------------------------
Resolution: Rejected
Servlet specification, 4.6 Resources:
The getResource and getResourceAsStream methods take a String with a leading
“/” as an argument that gives the path of the resource relative to the root of the
context or relative to the META-INF/resources directory of a JAR file inside the
web application’s WEB-INF/lib directory. These methods will first search the root
of the web application context for the requested resource before looking at any of the
JAR files in the WEB-INF/lib directory. The order in which the JAR files in the
WEB-INF/lib directory are scanned is undefined. This hierarchy of documents may
exist in the server’s file system, in a Web application archive file, on a remote server,
or at some other location.
Overlays do not work as expected
--------------------------------
Key: JBWEB-279
URL:
https://issues.jboss.org/browse/JBWEB-279
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core
Affects Versions: JBossWeb-7.2.1.GA
Reporter: Mustafa Musaji
Assignee: Remy Maucherat
Attachments: overlay.patch
It is expected that the <overlay> element in jboss-web.xml has the same outcome as
the overlay feature in the CLI:
https://docs.jboss.org/author/display/AS72/Deployment+Overlays
In jboss-web.xml the overlays element is not used to actually overlay existing files but
to add files to a deployment. This is confusing and either this should work the same as
the CLI or the documentation around the <overlay> element in jboss-web.xml should
clearly state this is not the case and that we do not replace artifacts but rather
Attached is a proposed patch that fixes this issue.
--
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