[
https://issues.jboss.org/browse/ARQ-826?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-826:
------------------------------
Summary: Servlet Protocol should verify the content of web.xml and
appliation.xml before applying its own packaging process (was: Servlet Protocol should
verify the content of web.xml/appliation.xml before applying its own packaging process)
Description:
To avoid invalid web.xml or application.xml files, the Protocol should verify that what it
is adding to these files is not already present.
This should be done to avoid duplicate servlet definitions in web.xml or duplicate web
modules in application.xml, in cases where the imported Archive is already enriched.
was:
To avoid invalid web.xml/application.xml files, the Protocol should verify that what it is
adding to these files is not already present.
This should be done to avoid duplicate servlet definitions in web.xml or duplicate web
modules in application.xml, in cases where the imported Archive is already enriched.
Forum Reference:
https://community.jboss.org/message/723345#723345 (was:
https://community.jboss.org/message/723345#723345)
Servlet Protocol should verify the content of web.xml and
appliation.xml before applying its own packaging process
------------------------------------------------------------------------------------------------------------------
Key: ARQ-826
URL:
https://issues.jboss.org/browse/ARQ-826
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Packaging Enricher SPI
Affects Versions: 1.0.0.CR7
Environment: Jboss 4.3 EAP/4.2.1, Java 1.5
Reporter: Patrick T
Priority: Minor
To avoid invalid web.xml or application.xml files, the Protocol should verify that what
it is adding to these files is not already present.
This should be done to avoid duplicate servlet definitions in web.xml or duplicate web
modules in application.xml, in cases where the imported Archive is already enriched.
--
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