Antoine, I think this was discussed 3 days ago in the thread titled "Form#anyComponentError change in 1.4 breaks validation" (Russel Morrisey), basically noting that in a recent release of Wicket, the form "onError" behavior was changed to checking for errors on ANY component in the form, to just Form-based components.
Related JIRA Issues: http://issues.apache.org/jira/browse/WICKET-2202 http://issues.apache.org/jira/browse/WICKET-2026 And eventually this issue created: https://issues.apache.org/jira/browse/WICKET-2734 Hope that helps incase you wanted to jump in on any of that. -R On Thu, Feb 11, 2010 at 10:02 AM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: > please create a quickstart and attach it to jira > > -igor > > On Thu, Feb 11, 2010 at 6:53 AM, Antoine van Wel > <antoine.van....@gmail.com> wrote: >> hi, >> >> In a nested form the onValidate() is overridden. >> It sets an error message on a component inside this form - so not on >> the form itself. >> >> However the submit on the form itself is executed as if no error >> exists. What I see when debugging is that hasErrorMessages on the >> inside nested form returns false. Is this correct? Should I explicitly >> set an error on the form, or something else to indicate the form >> itself has an error? >> >> ..using 1.4.6 >> >> >> Antoine. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
