[
https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin....
]
Mustafa Musaji commented on JBWEB-279:
--------------------------------------
[~rmaucher] I don't think overlays has anything to do with the spec. This is when you
are a deploy to JBoss and yes we should follow the spec to look for resources as stated in
your first comment. In addition to the spec, we allow overlays to be included and this is
as [~tfonteyn] points out, is a JBoss specific feature. With the overlays we blatently do
one thing via CLI and another thing with jboss-web.xml.
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: fix.proposal.txt
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