I hate to repeat this again, It feels to me that Wicket has too much default processing and callbacks. I would prefer things to be simpler. Hit a button - call a button handler. Submitted form without button - call default handler. And do whatever you want from this handler: call form's submit, validation, model, etc. Is not it simpler and more observable? Or is it just Struts legacy? ;-)
Michael. On 10/3/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > that you don't know in the submit of the form if a button did process it or > not. > we could give the Form.onSubmit() a boolean that a button was found? > > > On 10/3/05, Eelco Hillenius <[EMAIL PROTECTED] > wrote: > > I don't like controlling that kind of processing with boolean return > > values. What's wrong with the current state implementation of Form? ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
