Martin Cooper wrote:
This is the part that I've never understood. If it's intended to be a
helper
class, then why, oh why, do you insist on using an Action for this? If it's
a helper class, *make* it a helper class, not an action! And if the reason
is that you also use it as an action, then my response to that is that you
have the wrong structure - the common code should be in a helper class that
both actions use, instead of having one action invoking the other.
And there was a time I would have argued with you on this, but no more,
as I mentioned in another reply to Paul. I 100% agree when the
secondary Action isn't going to be called on its own, it definitely
should be a helper... and I probably 99% agree when it is going to be
used on its own... I don't take *quite* as hard a stance as you on it in
that case... take something like a render-phase Action... what's the
problem with having that Action called from the one that just handled a
form submission? I've never heard a good reason that its a bad idea...
even still, yeah, I do in fact basically agree with you now and tend not
to do it any more (can't remember the last time I did in fact).
Frank
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
(2006, Apress, ISBN 1-59059-695-1)
Java Web Parts - http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
