Struts uses a connection pool. So when you do a getConnection() you're
actually pulling one out from a pool of shared connection objects, so
there is no real problem with generating a new connection.
In my application I have manager objects will deal with data beans, and
these managers have
--- Vanderlei Silva [EMAIL PROTECTED] wrote:
The
problems with this approach are: the DAOs are not a
member of the Business
objects, but work in parallel with them. Thus, the
controller deals with
both the business objects and the DAOs, and makes
all the control, serving
also as a
Why not have your Managers create a connection as well
as taking in a connection?
Calvin
--- Shunhui Zhu [EMAIL PROTECTED] wrote:
That opens up lots of questions I also have, I'm
sure many of you have
some
solutions to these:
(1)I went through a similar exercise, I first
followed the
Title: RE: Struts and DAO pattern. Expensive?
That opens up lots of questions I also have, I'm sure many of you have some
solutions to these:
(1)I went through a similar exercise, I first followed the Petstore example,
to have a getConnection() method in my DAOs (well, I have BaseDAO
I need to confess I'm lost. The PetStore approach sounds cleaner in some
sence, but also sounds too repetite in other, and mostly, sounds way to
expensive (or it isn't?).
Struts uses a connection pool. So when you do a getConnection() you're
actually pulling one out from a pool of shared
5 matches
Mail list logo
