> > One option you have is to put the classes that actually cache things into > a common directory ($TOMCAT_HOME/lib or $CATALINA_HOME/lib). Such classes > are shared across web apps, so this should accomplish your goal of having > a single cache. They are loaded from a (common) parent class loader to > the one for each web app. > I'm not using the latest servlet spec (2.3). Anyway, the simplest solutuion will be to put all my classes on the system classpath, this should work. I have no jsp's and don't need dynamic class reloading in production, so I beleive it's perfectly legal in my case. Thanks and regards, --V.
- 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
- Re: multiple context pa... 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