Thiago H. de Paula Figueiredo wrote: > >> But one suggestion. Maybe tapestry should log on warn level if someone >> creates onValidate method with no parameters, else someone may be as >> confused as I was. I don't see any purpose of onValidate without >> parameters. > > That's a very good idea. Maybe Tapestry should go further and throw an > exception, as a no-arg onValidate method is useless. Please file a JIRA in > the Tapestry bug tracker for that. > I can't agree on that. This could break some apps that were using my kind of workaround (adding additional hidden fields) to make onValidate() work properly. I will create ticket, but later. Now time to go home and test new design :P -- View this message in context: http://tapestry-users.832.n2.nabble.com/Validation-in-component-using-onValidate-method-tp5315887p5316675.html Sent from the Tapestry Users mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
