[jboss-jira] [JBoss JIRA] (AS7-2974) Web fragments and annotations are processed although web.xml is metadata-complete
[
https://issues.jboss.org/browse/AS7-2974?page=com.atlassian.jira.plugin.s...
]
Robert Panzer commented on AS7-2974:
------------------------------------
This is a scenario, that does not work correctly imho:
I have a web-fragment defining a resource-ref called "MyResource".
This web-fragment is added to a web app, that does not define this resource ref and is
metadata-complete.
So a servlet looking up "java:comp/env/MyResource" should not succeed.
I tested this against WAS 8.0 and it treats it like I expected, i.e. the lookup fails.
On the current JBoss 7 with metadata-web 7.0.0.Beta30-SNAPSHOT this test fails by getting
a javax.sql.DataSource from the lookup.
Web fragments and annotations are processed although web.xml is
metadata-complete
---------------------------------------------------------------------------------
Key: AS7-2974
URL: https://issues.jboss.org/browse/AS7-2974
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.Beta1
Environment: JBoss 7.1.0.Beta1 (Current Snapshot), Win7 64Bit, Jdk 1.6.0_29
64Bit
Reporter: Robert Panzer
Assignee: Remy Maucherat
When deploying a web application the WarMetaDataProcessor merges information from
web-fragment.xmls and annotations although the web.xml has an attribute
metadata-complete="true"
The specification is pretty clear about how this scenario has to be handled and defines
in chapter 8.4:
Deployment descriptor metadata-complete process annotations and web fragments
web.xml 2.5 Yes No
web.xml 2.5 no yes
web.xml 3.0 yes no
web.xml 3.0 no yes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira