You will want to have the connection pool created when you start your server - some
servers like BEA Weblogic also have built-in connection pooling, so if you
configure it properly the connection pool will be instantiated when you start the
server. Then, from your bean you just get a connection from the connection pool,
rathar than from the db. WHen you are finished with the connection, you then
return it to the pool and it can be used by another request.
Hope this helps,
Ted
Jeff Behl wrote:
> What's the best way to do this on a bean that only has request scope? it
> doesn't make much sense to have a database pool instantiated every time
> the bean is. Without goign to an EJB model, is placing a database pool in
> the bean via a scriplet a viable option?
>
> basically, I want to use the same bean on a number of product web pages to
> display product specific information. Current plan is to have a
> setProperty method that sets the ProductID (primary key) on each page
> which allows the bean to grab the product information. If anyone has a
> better way to do this, I'd love to hear about it.
>
> thanks
>
> --
> Jeff Behl [EMAIL PROTECTED]
>
> ===========================================================================
> 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
--
---------------------------------
Ted L. Fritsch
The Revere Group
Phone: (847) 790-9800 x4103
Email: [EMAIL PROTECTED]
===========================================================================
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
