struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig McClanahan" <craig...@apache.org>
Subject Re: Reasons for 1.3 release
Date Mon, 20 Feb 2006 05:58:03 GMT
On 2/19/06, Martin Cooper <martinc@apache.org> wrote:
>
> On 2/19/06, Frank W. Zammetti <fzlists@omnytex.com> wrote:
> >
> > Does "MyCommand" represent a chain in MyCatalog?
>
>
> Yep.
>
>   If so, while I
> > wouldn't presume to speak for Craig, it sure seems like it :)  I've
> > personally used the "fire a chain from an Action" in the past, but I can
> > certainly see where this would be very nice.
>
>
> This is what I meant when I said earlier (in this thread) that I don't
> have
> any Action classes in my 1.3 app. I don't need 'em any more, even just to
> invoke a chain.


What you describe is indeed possible today, but it has a subtle difference
in implementation requirements:

* What you can do today -- implement your Action logic as a command,
  and build a customized chain that includes it.  (That's what you have
  described as your current solution, so you won't have any migration
issues.)

* What would be nice for migrating 1.2 apps -- support some mechanism
  to customize a per-Action chain that included calling the Action.execute()
  method so it does not need to be re-implemented.

The latter would let you take an existing app and later decorate individual
actions (just like WebWork lets you add intercepters) without requiring any
change to the initial implementation of the Action itself.  That's not the
way I would ever write a new app based on Action 1.3, but it'd sure help
migrating users.

--
> Martin Cooper


Craig

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message