> > Struts provides a basic Connection Pool, but user comments suggest that > > this is not suitable for large-scale, high-traffic applications, and > > also that it will soon be removed from Struts in favour of a > > container-managed connection pool > > So what will Tomcat Users do? Will Tomcat get a container manages connection > pool? > What is the reason for removing it form Struts? Struts, as I see it, is just an application framework. Connection pooling is a job for the JEE container, be it Tomcat or JBoss (or any other commercial). Nix.
- Re: Tomcat 4.x and Database Connection Poolin... Nikola Milutinovic
- Re: Tomcat 4.x and Database Connection Pooling rainer jünger
- Re: Tomcat 4.x and Database Connection Pooling Ric Searle
- RE: Tomcat 4.x and Database Connection Poolin... Jim Urban
- Re: Tomcat 4.x and Database Connection Po... rainer jünger
- Re: Tomcat 4.x and Database Connection Pooling Craig R. McClanahan
- Re: Tomcat 4.x and Database Connection Poolin... rainer jünger
- Re: Tomcat 4.x and Database Connection Po... Craig R. McClanahan
- Re: Tomcat 4.x and Database Connectio... rainer jünger
- Config Q: Using beans without creating context Joe Sternlicht
- Re: Tomcat 4.x and Database Connection Pooling Nikola Milutinovic
- Re: Tomcat 4.x and Database Connection Pooling Ken Anderson
- Re: Tomcat 4.x and Database Connection Pooling Soefara Redzuan
- Re: Tomcat 4.x and Database Connection Pooling Craig R. McClanahan
- Re: Tomcat 4.x and Database Connection Pooling Soefara Redzuan
- Re: Tomcat 4.x and Database Connection Pooling Soefara Redzuan