But according to servlet specifications container may
unload your servlet any time. Is not it ?
So you do something in the init(), preload this servlet
but what if later this servlet will be unloaded ?
One workaround is some singleton stuff, when you can check
pool presence in the "another" init'
27, 2000 8:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: ConnectionPool Object stored in ServletContext
>
> "Srini Sathya." wrote:
>
> > i too seriously thinking of this approach, i remember craig has sometime
> > back recommended this approach to one o
ent: Tuesday, June 27, 2000 5:03 PM
> To: [EMAIL PROTECTED]
> Subject: ConnectionPool Object stored in ServletContext
>
> I am planning on storing my ConnectionPool Object into the ServletContext so
> that all of my Servlets will be able to use one connection-pool, instead of
> creating
intended to offend anyone in the list, my apologies if this is gonna to
offend anyone ].
Regards
Srini
-Original Message-
From: Bragg, James [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 27, 2000 5:03 PM
To: [EMAIL PROTECTED]
Subject: ConnectionPool Object stored in ServletContext
I am
I am planning on storing my ConnectionPool Object into the ServletContext so
that all of my Servlets will be able to use one connection-pool, instead of
creating a different pool for each servlet. A Connection-Pool will be
create and stored into the servlet context at server startup. Is there any
