I am developing a database application and am using a similar MVC design to that in a
couple books I have. In those books they have a singleton class (a class in which
there will only ever be one instance) that accesses the database to create JavaBeans,
which are used to populate the JSP pages. These singleton classes also are used to
update the database with information from those JavaBeans.
Now I am assuming you have more that one of these singleton classes in larger systems.
Example, I am working on a billing inquiry system. So I have one singleton class for
the CustomerBean and a different singleton class for the Invoice Bean. (I could be
wrong in this assumption and there lies my problem.)
I would also like to use Database Connection Pooling. I would like to have one
collection of connections that are used by all the singleton classes. I would also
like to hide the fact that I am using a database to every classes except the singleton
classes. Right now I can not figure out how to use one common collection without
defining it in my Controller/Servlet class and then instantiating all my singleton
classes and telling them about the connection pool.
So what I am looking for is examples of class organizations of people using MVC and
database connection pools. Also would be interested in other online examples or e-mail
lists where I could get an answer to my question.
TIA,
Gerry Scheetz
Web Application Development
Global Information Technology Division
TRW - S&ITG
Helena, Montana, USA
[EMAIL PROTECTED]
(406) 594-1878
===========================================================================
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
