> Performance isn't so important as future-proofing - I don't want to have > to re-write the db interface when struts drops it's connection pool > provision, for example. > > I believe that mm.mysql does support pooling, although I take your point > that others may not. I can't see us moving away from MySQL at the > moment, so that's fine. > > My use of the database is really quite simple, so I'm sure that commons > would be fine, but at the moment I don't know where to start integrating > it with my Struts project. Does the container manage the pool (i.e. > some server.xml configuration needed)? Or do I instantiate and manage > the pool from within my application, and if so, how? I believe the correct approach is to let container handle setting up the pool. Look at JNDI-Resources HOWTO in Tomcat's docs. Nix.
- Tomcat 4.x and Database Connection Pooling Ric Searle
- Re: Tomcat 4.x and Database Connection Pooling peter lin
- Re: Tomcat 4.x and Database Connection Poolin... Ric Searle
- Re: Tomcat 4.x and Database Connection Po... Nikola Milutinovic
- Re: Tomcat 4.x and Database Connection Pooling rainer jünger
- Re: Tomcat 4.x and Database Connection Poolin... Ric Searle
- RE: Tomcat 4.x and Database Connection Po... Jim Urban
- Re: Tomcat 4.x and Database Connectio... rainer jünger
- Re: Tomcat 4.x and Database Connection Poolin... Craig R. McClanahan
- Re: Tomcat 4.x and Database Connection Po... rainer jünger
- Re: Tomcat 4.x and Database Connectio... Craig R. McClanahan
- Re: Tomcat 4.x and Database Conn... rainer jünger
- Config Q: Using beans without creating contex... Joe Sternlicht
- Re: Tomcat 4.x and Database Connection Poolin... Nikola Milutinovic