Just a simple design question. Having read through several posts and reading
the Struts documentation. I was wondering what is the best design pattern
regarding SQL placement. My thoughts were that I need to keep SQL out of the
action class and pass all resultset data into Collections of beans. This
helps keep from having tons of connections and resulsets sitting out there
tieing up valuable database resources. The collection of "databeans" are
then placed in a scope using the Controller(Action class)and made available
to other logic processes in the scope and/or passed on to the view for data
display. I am assuming this is because "business logic beans should be
designed and implemented so that they do not know they are being executed in
a web application environment." Is my interpretation that SQL is part of the
Model and should be placed in Logic beans tweaked? Or is this a 6 and half
dozen scenario? Or is there another pattern that I am missing altogether?

Brandon Goodin
Phase Web and Multimedia
P (406) 862-2245
F (406) 862-0354
[EMAIL PROTECTED]
http://www.phase.ws



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to