DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26810>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26810 root context loaded again under its docbase name [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-02-10 10:21 ------- As Remy has shown, it can be inhibited, but at the cost of losing the autoDeploy and deployOnStartup behaviours. I cannot see any advantage to this behaviour, but I can see some disadvantages to it. (1) the 2nd context will consume resources (2) if an inquisitive surfer finds the 2nd context, the webapp may not work because it is not in the root context and its intra-app URLs may break. And of course (3) it's not impressive ;) - Tomcat's behaviour with this double-deployment is counter-intuitive, arcane and obscure. I thus rest my case before the jury: it is a bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
