> The servlet container may (and tomcat does last I > checked) create one instance of a > (non-SingleThreadModel) servlet for every <servlet> > tag in web.xml. So just have two <servlet> tags > with different <servlet-name> but same > <servlet-class> in your web.xml. You don't need two > contexts for this.
You nailed it right on the head. Thanks! I wonder aloud how Tomcat knows which class to use in any particular context (the <server> doesn't map to the <Context>), but maybe I'll just try it and see. So, to summarize...because I could find nothing on the topic anywhere and maybe this gets indexed somewhere...aliases and contexts do not map to different instances, <server>'s do. > > > The question is how I can replicate the above > > behavior so static variables are spanned across > > more than one instance? Can anyone point me at a > > Tomcat scoping document? > > The tomcat scoping document is the Servlet > Specification more or less ;) For things that are > left up to the container implementation, you'll need > to ask or better yet, read the code. > > Yoav Shapira > > > > This e-mail, including any attachments, is a > confidential business communication, and may contain > information that is confidential, proprietary and/or > privileged. This e-mail is intended only for the > individual(s) to whom it is addressed, and may not > be saved, copied, printed, disclosed or used by > anyone else. If you are not the(an) intended > recipient, please immediately delete this e-mail > from your computer system and notify the sender. > Thank you. > > > ---------------------------------------------------- >----------------- To unsubscribe, e-mail: > [EMAIL PROTECTED] For > additional commands, e-mail: > [EMAIL PROTECTED] -- - John Blanco - Code Guru @ Rapture In Venice - http://members.bbnow.net/jblanco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]