Well, creating a JavaBean, with DatabaseManager class, and load
DatabaseManager and that
JavaBean class on startup. (web.xml file), you can put all connectivity
to DatabaseManager
class, make up a doInsert(), doUpdate(), getValue() methods in it, with
empty query.
Once those puppies are loaded, them will be up all the time. Next thing
is to refer from JSP pages to those poppies, such as getValue(email), and
dbmanager will return it...
Now you can have them available to whole site, w/o reloading or
overloading your server.
got the point?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/5/01, 2:03:48 PM, "John Coonrod" <[EMAIL PROTECTED]> wrote regarding
Connection pooling - simplified?:
> Perhaps there is a way to do this very simply.
> I have only one database, and so little traffic that one connection is
all
> my webserver needs.
> I presume there might then be a way to establish a connection when
jakarta
> starts up, that is available to any jsp that wants it? Sort of a globally
> available connection? Could someone walk me through doing this?
> (Meanwhile - I've ordered the book from Amazon. Thanks.)
> Thanks.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
NOTICE: This communication may contain confidential or other privileged information.
If you are not the intended recipient, or believe that you have received this
communication in error, please do not print, copy, retransmit, disseminate, or
otherwise use the information. Also, please indicate to the sender that you have
received this email in error, and delete the copy you received. Any communication
that does not relate to official Columbia business is that of the sender and is
neither given nor endorsed by Columbia. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
