tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Brunkow <>
Subject RE: Database Connectivity, JDBC2 and Tomcat
Date Thu, 27 Jul 2000 23:37:37 GMT
The problem here is using tomcat and not having access to enterprise beans.
He's talking about saving the db connection in the user/servlet session,
which I don't quite agree with. Having a db connection per user is "not
optimal", although I appreciate the response. My understanding was that
JDBC2 required pooling under the covers which allows me as a user in the
servlet to get a connection much faster than in the JDBC1.X world.  Two of
my questions are, "are people using that" and "does it actually work".  This
is a big deal with tomcat since I can't use an enterprise bean.  I have to
use java beans(simple classes/non enterprise beans) and inside those classes
I want to abstract data tables.  Anybody else facing such issues?

Correct me if I'm wrong or mistaken on any of this.


-----Original Message-----
From: John Daniels []
Sent: Thursday, July 27, 2000 4:26 PM
Subject: RE: Database Connectivity, JDBC2 and Tomcat

By "session object," do you mean session beans?

>You can use the session object to cache the JDBC connection throughout your
>JSPs and Servlets. This way you are connected once and can reuse the
>connection. Also you can close the connection on session expiration. Well,
>about the JDBC pooling, that is totally depends on the implementation of 
>JDBC driver.
Get Your Private, Free E-mail from MSN Hotmail at

View raw message