I use a Singelton class ConnectionHandler to manage my connection pools.
This ConnectionHandler has static methods to get and close a connection.
When you get a connection you really get a wrapper for a connection (but it
implements sql.connection itself as well.) the close method of the wrapper
doesn't close the underlying connection but releases it in the pool.
Geert 'Darling' Van Damme
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of Cory L Hubert
> Sent: vrijdag 3 december 1999 16:55
> To: [EMAIL PROTECTED]
> Subject: Connection Pool
>
>
> Ok. I am on a roll now. I am trying to setup a
> Connection Pool. I have
> a few samples. But I don't know where to put it in my project. Should I
> put it in the Beans? Or should I just make one connectionpool
> jsp file and
> include it in all the pages?
>
> What is the best way? I know this is an opened end
> question but, I'd like
> to hear a few suggestions.
>
> ==================================================================
> =========
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
