DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33405>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33405 Summary: Fixing corrupted webapps web.xml requires tomcat restart. Product: Tomcat 4 Version: 4.1.21 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P4 Component: Servlet & JSP API AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I have servlets and JSP files hosted by a web hosting company. So I don't have access to the Tomcat Web Application Manager. If I've deployed a new servlet and want my web application reloaded, I've discovered that I can just touch my web.xml file and Tomcat will load the new servlets. However, if I make an error in my web.xml file, Tomcat will appropriately not load my application due to potential security risks. However, if I fix the web.xml file, Tomcat does not detect my update and does not attempt to reload my servlets. It would be nice if Tomcat would still monitor the web.xml file for updates even if the previous parse attempt failed. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
