You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by ji...@apache.org on 2004/04/17 18:55:30 UTC
[jira] Updated: (CACTUS-67) cactifywar makes it worse without error if source web.xml does not conform to DTD
The following issue has been updated:
Updater: Vincent Massol (mailto:vmassol@apache.org)
Date: Sat, 17 Apr 2004 9:54 AM
Changes:
assignee changed from Cactus Developers Mailing List
type changed from Bug to Improvement
description changed from I had a web.xml where I had put a listener too early, so it did not conform to
the DTD. As Tomcat treats this as a warning, I hadn't noticed.
However, cactifying the WAR added:
<filter-mapping>
<filter-name>filterredirector</filter-name>
<url-pattern>/test/filterRedirector.jsp</url-pattern>
</filter-mapping>
first (before the listener), which Tomcat didn't like very much because it
hadn't seen the filter definition yet, and failed to start.
cactifywar shouldn't have to correct other people's mistakes, but it would be
good if it gave an error if the web.xml did not conform to the DTD, so that this
mistake was not so well hidden :) to I had a web.xml where I had put a listener too early, so it did not conform to
the DTD. As Tomcat treats this as a warning, I hadn't noticed.
However, cactifying the WAR added:
<filter-mapping>
<filter-name>filterredirector</filter-name>
<url-pattern>/test/filterRedirector.jsp</url-pattern>
</filter-mapping>
first (before the listener), which Tomcat didn't like very much because it
hadn't seen the filter definition yet, and failed to start.
cactifywar shouldn't have to correct other people's mistakes, but it would be
good if it gave an error if the web.xml did not conform to the DTD, so that this
mistake was not so well hidden :)
environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
priority changed to Major
Fix Version changed to 1.7
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-67?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-67
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-67
Summary: cactifywar makes it worse without error if source web.xml does not conform to DTD
Type: Improvement
Status: Unassigned
Priority: Major
Project: Cactus
Components:
Ant Integration
Fix Fors:
1.7
Versions:
1.5-rc1
Assignee:
Reporter: Brett Porter
Created: Thu, 6 Nov 2003 10:03 PM
Updated: Sat, 17 Apr 2004 9:54 AM
Environment: Operating System: Other
Platform: Other
Description:
I had a web.xml where I had put a listener too early, so it did not conform to
the DTD. As Tomcat treats this as a warning, I hadn't noticed.
However, cactifying the WAR added:
<filter-mapping>
<filter-name>filterredirector</filter-name>
<url-pattern>/test/filterRedirector.jsp</url-pattern>
</filter-mapping>
first (before the listener), which Tomcat didn't like very much because it
hadn't seen the filter definition yet, and failed to start.
cactifywar shouldn't have to correct other people's mistakes, but it would be
good if it gave an error if the web.xml did not conform to the DTD, so that this
mistake was not so well hidden :)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org