Sounds like a plan, +1. If we do that, I would opt for removing the defaultFormProcessing parameter all together. Having the other two options are enough.
Eelco On 9/6/05, Phil Kulak <[EMAIL PROTECTED]> wrote: > After some thought, here's what I think would be great to have in the > Button component: > > /** > * When true, all components of the form are validated on submit. > Default is true. > */ > setValidate(boolean); > > /** > * When true, all form values are bound to their models on submit > after validation, if there is > * validation. Default is true. > */ > setBind(boolean); > > This would make setDefaultFormProcessing(boolean) set either both to > true, or both to false. What are the thoughts on this? I'd be happy to > do it and submit the patch if this is a change that the devs agree > with. > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
