Wow. Million different way for doing it. Here's mine:
I use single dispatcher servlet that hands off requests to worker classes. In this
servlet's init method I create one instance of DBConnection and put into services
hashtable to be passed to worker classes.
DBConnection in its constructor
Yap!, if you are creating the new instance of a DbBroker obviously it will be
create new instance for every other servlet( i mean Servlet A and Servlet B). So
have a wrapper over the DbConnection and use a singleton pattern
regards
ravi
Stuart Norton wrote:
> Hi,
>
> This is my first p
You need to create a servlet that does nothing but create the connection pool
then add the servlet to the servlet
context. In that servlet, lets call it ConnPoolServlet, provide at least two
methods, getConnection() and close().
You can add the servlet to the servlet context from the ConnPoolSer
You need to create a servlet that does nothing but create the connection
pool then add the servlet to the servlet context. In that servlet, lets
call it ConnPoolServlet, provide at least two methods, getConnection()
and close().
You can add the servlet to the servlet context from the ConnPoolServ
(don't know about others) it means that
servlets and Globals must be in wrapper classpath, not in repositories.
Cheers
DD
--
From: Stuart Norton[SMTP:[EMAIL PROTECTED]]
Sent: Thursday, February 17, 2000 03:06 PM
To: [EMAIL PROTECTED]
Subject: DbConnectionPool over mul
Hi,
This is my first post on the list, so I've finally come out of the woodwork!
I'm using the com.javaexchange.dbConnectionPool class (from
www.javaexchange.com) to access a database through an ODBC driver. This
works with one servlet, where I define a new instance of the class in the
init() of
