+1 That's cool. In my "day job", we've been going round and round on whether to go with PoolMan or DBCP. I'm -0 on PoolMan mostly because the author seems to want to dump it, but other folks are -0 on DBCP because it's not yet released.
Presumably, we can help push for a Pool release and then a DBCP release, and have all our ducks in a row for Struts 1.1. Not sure if I can help with that, but I'll take a look. Any thoughts on how the new kid on the (Commons) block - jdbc2pool - might fit in to the scheme of things? -- Martin Cooper ----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 6:50 PM Subject: Proposed Migration to DBCP Based Connection Pool > I am going to propose that we switch to a connection pool based on the > commons-dbcp (and commons-pool) packages as the "preferred" data source > implementation for Struts 1.1. The existing implementation already has > equivalent functionality to what org.apache.struts.util.GenericDataSource > covers, and it will shortly have some additional very useful things (such > as caching PreparedStatement instances for reuse). > > Towards that end, I'm adding dependencies in the Struts build scripts for > commons-dbcp.jar and commons-pool.jar. You'll want to update your build > environments to include definitions for these properties. > > Craig > > > > -- > 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]>
