In terms of the chain implementation of the request processing lifecycle, this is just an unconditional command in the chain (it's implemented in o.a.s.c.servlet.PerformForward). No skipping or stepping is requried. See
contrib/struts-chain/src/conf/chain-config.xml
for the entire definition. You'll note that it requires no skipping -- just the conditional behavior on validation failures, which is modelled as a branch to a separately named command.
I wonder if even these conditionals could be made part of the chain. As an alternative to branching, the Command could update the state of the Context and return false. What is now a conditional Command could be the next link the Chain. The "conditional" would check to see if the state calls for it to execute, and if so, do its business and return true.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
