On 1/30/06, Paul Benedict <[EMAIL PROTECTED]> wrote: > I didn't think of the CoR for the implementation. But I am curious: why not > just a setValidationStrategy() on the actionform?
First it's one thing and then it's another. There are alternate ways to handle double-submits, and autopopulation, and most everything else the framework does. Rather than nickel and dime the API, why not take a page from the WebWork playbook, and go for the break away? <<Now cut that out!>> After moving our singleton request processor to a configurable chain, the next logical step is to do what WebWork has done, give each Action the chance to use or extend the default request processor, or just roll its own. Essentially, each Action could declare its own "Controller". It doesn't have to be a case of "there can only be one." -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
