On Wed, 22 Aug 2001, Craig R. McClanahan wrote: > Since the original objective was to share the cache, it seems to me that > one versus two contexts is not a big deal, right? ahhh, sorry - missed the start of the thread... thought it was a more general "one webapp" thing... > > you would be well advised to put it in a jar which you then place in > > tomcat's lib dir... that way its relatively easy to move your app. > > > > In fact, this is critical to the sharing solution. Eerything in Tomcat's > lib directory is shared -- everything in /WEB-INF/classes or /WEB-INF/lib > is not shared. My reading of the suggestion was that the classes would reside elsewhere in the system but be in the startup classpath as startup - this would do the same thing but be a little more spread out... thats all my point was there (o: cheesr dim
- multiple context paths pointing to the same doc base? Vladimir Grishchenko
- Re: multiple context paths pointing to the same ... Craig R. McClanahan
- Re: multiple context paths pointing to the s... Vladimir Grishchenko
- Re: multiple context paths pointing to t... Craig R. McClanahan
- Re: multiple context paths pointing ... Vladimir Grishchenko
- Re: multiple context paths poin... Craig R. McClanahan
- Re: multiple context paths ... Vladimir Grishchenko
- Re: multiple context pa... Dmitri Colebatch
- Re: multiple context pa... Craig R. McClanahan
- Connection pooling Ques... Dmitri Colebatch
- Connection pooling Ques... A.L.
- RE: Connection pooling ... Filip Hanik
- Re: Connection pooling ... Bo Xu
- static variables in multiple contexts PLEAS... Zach Hollandsworth
- Re: static variables in multiple context... Craig R. McClanahan
- RE: static variables in multiple con... Zach Hollandsworth
- RE: static variables in multipl... Craig R. McClanahan
- RE: static variables in mul... Zach Hollandsworth