-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
The download page for this component says Tomcat 6. Is this component
compatible with Tomcat 5.5 as well? If
Christopher Schultz 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
The download page for this component says Tomcat 6. Is this component
-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
http://tomcat.markmail.org/message/4acbkimgilfkcdru?q=+list:org%2Eapache%2Etomcat%2Edev+
-Tim
Christopher Schultz 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
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: [ANNOUNCE] Beta candidate for Tomcat 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?
https://issues.apache.org/bugzilla
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Len,
Len Popp wrote:
A brief list of reasons is given in the link from Filip's post:
https://issues.apache.org/bugzilla/show_bug.cgi?id=46038
Whoops! Sorry. I should have read that before I opened my big mouth.
The most important reason IMO is
