Hi All,

Thanks for your thoughtful and enlightening threads of discussion on the
Model 2 architecture. I have been building a web site using Servlets, beans,
java classes and JSP based on this model. The one question I have which
seems to be missing from these discussions is where do I store the
Connection Pool? My current thoughts are to initialize the connection pool
in the controller servlet init() function, create the Pool as a Singleton,
then any java class at the persistence level that needs a connection just to
call ConnectionPool.getInstance(). Is this what most people are doing? The
other option I suppose is to pass a connection through the Java Bean Action
class, down through the persistence java classes.

In a similar vein, how do people handle logging. I wish to have one logger
class accessible by all classes in my application. This includes the
Servlets, beans and regular java classes.

I've programmed with a proprietary Application Server Web Objects, that had
one Application class that was accusable by all other classes in the
application. Here I stored the logging, and any other global services. How
would I handle this with Servlets, JSP, bean Model 2 architecture.

Thanks for your time in this matter.

-Steven Rock
hitmusic.com  - choose and watch music videos of today's top hits.

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
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

Reply via email to