We have an application in development stage. Instead of a connection
pool I have chosen to give each logged in user its own Connection which
is stored, together with other session stuff, in a session bean (i.e.
sessionBean.getConnection() wherever DB is needed).
I haven't seen anyone else use this method, but it works great in my dev
environment.
Am I missing something?
Could this cause problems in deployment?
Mattias Jiderhamn
Expert Systems
[EMAIL PROTECTED]
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and
reference
> Sent: den 5 juli 2001 22:47
> Subject: Best way to load up a connection pool?
>
> The question I have is there a "best" way to load up the
ConnectionManager
> for the application? I was just going to use a <jsp:useBean ..> tag on
> every jsp page with the ConnectionManager having application. Is there
a
> better way to do it so that all of the methods called from the classes
> have access to the connection pool? Since before any user can use the
> application they will have to go to a login page I was thinking maybe
> there is something I can do just once on the login page that will set
up
> the ConnectionManager and I then wouldn't need to have to include the
> useBean tag on the top of every other page. Maybe I'm doing it the
best
> way, but I'd like some suggestions if there are other ways.
> Thanks so much,
> Rick
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
