On 9/6/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
This sounds to me like a rather blatant mis-use of actions. In the first
place, as Michael points out, action chaining has always been an
anti-pattern in Struts. As such, I'd be against promoting / encouraging the
use of chaining in the way you describe (or in any other way, for that
matter ;).

We actually use chaining a lot. We don't use ChainingInterceptor, and
our chained actions have little to no direct interaction. What don't
you all like about it?

More importantly, it demonstrates the mis-use, IMHO, of actions as the basic
unit of server-side logic, instead of simply the end-point for a request. An
action represents the processing surrounding a complete request, not a part
of a request. If there is a need to break that request processing into
smaller units - and there frequently is - then the action should be the
orchestrator of those units. For example, a common case would be one unit to
handle the incoming request and a second to handle preparing to display the
next page. Those two units would be two separate classes, not two actions
chained together.

Why?

Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to