The best place to keep a connection pool is in a bean with the application
scope. The application scope will load the bean only once and keep it
around. All JSP pages can then access this bean to use the connection pool.
-----Original Message-----
From: Pankaj Malviya <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, August 11, 1999 1:13 PM
Subject: Re: JSP Application-Scoped Beans
>How do you keep a pool of DB connections. My
>assumption is everytime a new Instance will be created
>whenver useBean is used.
>Whether scope = application makes a difference.
>
>
>> > I would like expose a Database Connection Pool
>> which we have written in
>> > all our
>> > JSP pages. It is not a JavaBean. In fact, there
>> seems to be no redeeming
>> > reason for
>> > me to convert this class to a JavaBean, other than
>> to be able to expose
>> > it to my JSP
>> > pages through the <jsp:usebean
>> scope="application"...instruction.
>> >
>
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff JSP-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
