Martin Cooper wrote:
For six years or so, I've watched people repeatedly shoot themselves in the
foot becuse they think they want to chain actions and they _don't know_ the
consequences or their - uh - actions. The serious problem is that many -
perhaps most - developers have no idea what is going on under the covers,
and they _will_ get into problems with chaining actions, and will have no
idea _why_ they are getting into problems. There's no way I want to see us
encouraging the use of an anti-pattern that is an anti-pattern for very good
reasons. Just because it _can_ be done doesn't mean it _should_ be done. We
are here to help users to build their applications as simply as possible.
Using techniques that have traps and pitfalls that are easily stumbled upon
is not a good way to do that.

But don't we also need to explain *why* something is an anti-pattern too? I don't know about anyone else, but I don't accept anything as a "best practice", or pattern or anti-pattern, until I understand why it is so, and ultimately agree with it (which means I sometimes have to change my stance on things as I understand more, but I have no problem with that). Understanding and not just accepting advice also allows you to make better decisions in the future as you can apply knowledge to other domains. It's also partly how less experienced programmers become more experienced and able to think for themselves rather than just following others' words.

So, *why* is action chaining bad? What are the traps and pitfalls? Why is instantiating and calling one Action from an other bad (I understand this isn't action chaining, hence two separate questions, but the question fits here too).

Martin Cooper

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]

Reply via email to