Michael Jouravlev wrote the following on 7/6/2005 5:03 PM:
The action class
provides the event contract, while the action form does the dirty
work.
Well in this case the struts-config file would provide the contract and
you could simply use one ForwardAction for everything. You've
substituted numerous Actions (or DispatchAction methods) and replaced
them with either A) numerous ActionForms (probably sharing the same
field names or B) complext logic in single ActionForms to decide on what
'business logic' to do.
Did I convince you that having business logic in an action form is
better? Action class provides external I/O contract and manages
messages and navigation, while action form performs operations on
business data, *where it is actually stored* .
No you haven't convinced me at all:) I still see no practical benefit to
flipping struts inside out like this. Sure it'll work, and I'm not even
saying (without a lot more thought:) that it's "bad," but it certainly
totally turns around the way the framework was designed to work. (I
don't think the method names "reset" and "validate" would be chosen as
method names in an ActionForm if they were designed for doing all kinds
of business logic in them.
I think if you go this route, you should say it's a different version of
Struts.. maybe StrutsWorks or something:) Under the scenario you've
proposed I don't see what the point of using any Actions would be? Why
not just use the one default FowardAction and do everything in the
ActionForm?
(In case someone is popping into this thread late, I'm certainly not
advocating this:)
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
