A brief list of reasons is given in the link from Filip's post: https://issues.apache.org/bugzilla/show_bug.cgi?id=46038 The most important reason IMO is that you can't build Tomcat with a recent JDK. See: https://issues.apache.org/bugzilla/show_bug.cgi?id=43147 -- Len
On Thu, Nov 13, 2008 at 12:12, Christopher Schultz <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Filip, > > Filip Hanik - Dev Lists wrote: >> The Apache Tomcat team announces the immediate availability of >> Apache Tomcat JDBC Connection Pool > > I'm sure this is documented somewhere, but why is Tomcat creating its > own connection pool instead of continuing to use commons-dbcp? Not > trying to start a flame war... just curious. No need to repeat arguments > found elsewhere if you'd just like to provide a link. > > Thanks, > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkkcX/QACgkQ9CaO5/Lv0PAMmQCgjTm8n/n5OhKBOy1IEuyJ4bQP > Os4AoJr065w4kK22RnhK05rnHfn8Y/K4 > =S1jX > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
