--- Martin Cooper <[EMAIL PROTECTED]> wrote:
<snip/>
> Hmm. These days, I'm leaning towards thinking of Actions as something we
> retain for backwards compatibility only, once we're in a Struts 2.0
> world,
> so I'm not sure I'd consider a scriptable action, let alone just a plain
> Action, as something that would go in the core.
>
> I should probably elaborate a little on the perhaps heretical statement
> above. ;-)
>
> For a long time now, I have considered Actions as almost an
> anti-pattern.
> The need to separate the incoming request handling from the outgoing
> view
> preparation is fairly clear to many people, I think. Today, Struts does
> not
> provide a real solution to this problem, especially for applications
> which
> must be customisable without requiring changes to the Actions
> themselves. As
> a result, many, many people try to do this by chaining Actions, and
> thereby
> get themselves into trouble that they don't understand.
>
> Instead, I'd prefer to see us move away from Actions as the core
> actionable
> objects, and towards something like a request handler and view preparer,
> or,
> more generally, a chain of commands, a la Commons Chain. Today's Actions
> would be a degenerate case.
I agree; I always found Tiles' Controllers to be more useful than Actions
for setting up a view because you attach the preparation code to the
actual view instead of trying to remember which URL causes this view to be
displayed. However, you can't always use a Tiles Controller and need an
Action to make decision logic. It would be nice to have a view
preparation system in the core and move away from Actions.
David
<snip/>
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
