[
https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin....
]
Remy Maucherat commented on JBWEB-279:
--------------------------------------
I thought my sentence was clear enough: "This code is the implementation for the
specification /META-INF/resources mechanism. As a result, it must follow the
specification's behavior. I'm sorry, but there is little way around that."
This is not the implementation for a JBoss specific feature, this is the specifcation
standard feature. The xml configuration allows specifying a JAR as if it was included
directly in the WAR itself. AS added at some point another feature called
"overlay", which is not the same thing (here, it is a proprietary feature
unrelated to any EE spefication).
So, well, have fun with the JIRA, but this is a "bug" that will not be fixed.
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