Schaub, Stephen wrote the following on 7/11/2005 3:56 PM:
Yes -- it is supposed to be abstract -- each ActionForm subclass must
define an execute() method to perform the processing for that form.
(Right but in your example you were showing LoginAction as the
implementing class and you still kept it abstract in the example-
probaby just cut and paste errror no big deal)
If you like this approach definitely check out StrutsDialog.
Thanks for the tip. I took a brief look, but I don't see how
StrutsDialogs corresponds to what I'm suggesting. It appears to
maintain a separation of Action and ActionForm, which I am proposing
to combine.
Actually you might want to get with Michael, he has been talking about
combining the ActionForm and Action together, and I too think that's the
best approach to take if you plan to push the business logic into the
ActionForm.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
