struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Husted <>
Subject Re: Reasons for 1.3 release
Date Fri, 17 Feb 2006 00:11:55 GMT
On 2/16/06, Craig McClanahan <> wrote:
> Ted has some good use case examples in his Agility stuff.

Yes, we've been basing our ASPX applications on a port of Commons
Chain for well over a year now. We bind and read the controls to a
Commons Context in the code behind, and execute Commands from a
Catalog as needed. We find that a Chain of Command handles business
logic quite well. A Chain is also a handy way to bind rich controls on
a page, since you can have a command for each control and then add or
remove the commands as the page changes.

The Chain of Command is in no way specific to the request processor.
It's just that the Request Processor is a good use case for a Chain of
Command. It's very much the same idea as the WebWork interceptors. The
next step in that regard would be to let each Action have it's own
request processing chain, instead of insisting there only be one. A
very useful pattern there is to define a pre-opt and post-op chain.
Then, at runtime, create a new chain around the "Action" command:
instant interceptor!


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message