Hi, I am trying to write a web-app using servlets (using "Java Servlets Developer's guide" by Karl Moss as a reference). I have created my connection pool, established a connection, logged myself and moved on into my app. My question deals with the creating and closing of the connections... In the example in the book the application is a one servlet class app (a login screen) and the connection, statment and resultset are created on doGet(), information is shown and then the these objects are all closed. If I move past the login screen in my application, should i close the connection and then re-open it?!? seems like overkill - or can i assign my jdbc connection to the session? What is the correct way to handle a connection between multiple screens. Think Im going to do some more reading, but any advice is appreciated. Thanks, Chris
SCJP 1.2, SCJP 5, SCBCD
Joined: May 22, 2003
think i just found my own answer ... using a connection pool. is it still correct to close the connection each time I leave a page tho ?!?
Chris, The subject of connecting to databases is one of great importance due to connections be so time consuming. Most application servers and containers come with in built facility for connection pooling. For example, I use Tomcat which has a JNDI Datasource. What you might want to do is to have a Database class that takes care of the connection to the database and then use this whereever required. HTH
The secret to creativity is knowing how to hide your sources.
Hi, It is always a good practice to do the DB connectivity in the init() of servlet and by using the servlet instance pooling which many servlet containers and app servers support you need not worry abt the DB connectivity pooilng separately. Cheers, Gaya3