Ted, will you give me your opinion on my post of "Mon 1/27/2003 5:21 PM" with a subject of "RE: Two ActionForms colliding on property name"? I am wondering whether you see my splitting of actions into post-actions and pre-actions as action relays or action chaining.
To use the input attribute in validation to point to a previous action, the input element needs to point to what I call a pre-action but not the post-action. So this requires a separation between pre-actions and post-actions. I am not arbitrarily partioning the request/response transaction; I am drawing a well-defined line between processing necessary to complete the last user/system interaction and processing necessary to initiate the next user/system interaction. Overall, I am not grokking your division between "completing the response" and "continuing processing." Perhaps because, in my mind, completing the response requires continued processing and why continue processing if not to complete the response (unless it is to complete the request, as in my post-action). > -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 1:07 PM > To: Struts Users Mailing List > Subject: design question about action chainning(As quoted in > :Struts in > action...by Ted Husted et al..) > > > The best example of waht I'm calling an Action relay is how Struts > handles validation. If validation fails, the request is > forwarded to the > input property, which could be another Action. This is done > to complete > the response, rather than continue with processing the action. > > This same technique is often used after a lookup, where one > Action does > the lookup but another Action is used to complete the > response, usually > to setup any tools the page might need to render. > > In an Action chain, control is not forwarded simply to complete the > response but to continue processing. One action doesn't "do" some > similar activity because that's the another actions "job". The > request/response transaction begins to be distributed between several > Action, and this is where Action stop being destinations and start > becoming an API. > > Most often, whatever processing the Action in a chain are > supposed to be > doing can be refactored into base actions or utility classes, so the > funcationality can be reused using standard object-orientated > techniques. > > -Ted. > > > -- > Ted Husted, > Struts in Action <http://husted.com/struts/book.html> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
