Travis: I like org.apache.commons.dbcp. It's simple, it works, and it's easy to throw into Tomcat for use with JNDI. (Tomcat ships with Tyrex, which is broken if you want a pooled datasource without XA.)
In general I like the idea of connection pools being provided by the container through JNDI, so you get all the site-specific configuration out of /WEB-INF and you can make your application pool-independent. (Use WebLogic pools if you got 'em, etc.) I've been meaning to get around to JNDI support for Torque for a while, to let Torque easily use whatever pool is available. -- Bill ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 26, 2002 7:42 PM Subject: Connection pools > Just curious which connection pool is the best to use? Any plans to standardize on one? Maybe a generic pooling interface that all of these could implement? > > I've noticed several Connection Pool classes throughout the various projects, ie: turbine has one, commons has one, and i'm sure i've seen it elsewhere too. > > Travis Reeder > Chief Software Architect > www.ThinkVirtual.com > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
