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=40811>. 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=40811 ------- Additional Comments From [EMAIL PROTECTED] 2006-10-24 09:24 ------- > Remove > <Context path="" > docBase="search.hyperpal.com" reloadable="true" debug="0" > /> > Thanks for the help - I really appreciate it. Indeed, this solved the double instantiation. But without the context information, I am no longer able to access my application at http://x/index.jsp, because tomcat no longer associates the root level with my search.hyperpal.com folder. It just falls into the old ROOT folder. Is the essential problem here that my app lives in Tomcat's webapps folder? If so, is the correct solution then to move the app out of webapps and keep the <context> thing in server.xml, only with a docbase pointing at the out-of-webapps folder? Regardless of the hows and whys, I still maintain that strictly speaking Tomcat should never try to initialize the same context twice. This simply isn't correct behaviour even if the user by means of configuration (or lack thereof) indicates that he wants this to happen. Especially since the programmer has no way to avoid being initialized twice by conventional means (static class member variables). -- 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]
