Thanks again Ted,
I didn't mean to imply that my View developers were also developing
their own Tags. They aren't. Instead, I develop the Model, which
includes back-tier business logic to perform actions, and return a bean
(or a collection of beans) as a result. High-level business method names
l
Bryan Field-Elliot wrote:
> This is where I am having a problem -- if the Action is always
> responsible for creating whatever JavaBeans the View needs, then doesn't
> that unnecessarily couple (tightly) the View and the Controller?
Personally, I advocate the Layers pattern for web applications,
Thanks for the long opinion Ted. I agree with most of what you
discussed, which is that the Actions should be delegating to a "real"
business layer of back-end classes and methods, which can be re-applied
to a non-Struts front-end.
It's your first paragraph which I'd like to continue to discuss (
Personally, I would suggest that an Action should always be used to
create whatever JavaBean helpers the view needs. The views only
responsiblity should be to render the beans. Where these beans come-from
or go-to is the controller's business.
This puts all the business logic behind Actions, and
Hi all,
I wanted to collect a few opinions on programming style with respect to
Struts and JSP.
The following have been my guiding principles for the last several
Struts projects I've done:
1. When a JSP page needs to ALTER the model (e.g. data will be written),
a Struts Action should be used.
5 matches
Mail list logo
