Thanks, Thiago. Yes, the wiki page should explain other ways of recording errors instead of this one that, as you said, it is known as bad idea.
By the way, I have I doubt about this: one thing useful of this onValidateFromComponentId methods that throw Exceptions is that you can validate specific fields and record errors on them without the need to inject the component just to pass it to Form#recordError… is there another way to record an error on a Field without the need to inject the Field just for this? (just like you can return return a link to a page with just returning the page class or page name as String, without injecting the page on the component). Thanks. -- View this message in context: http://tapestry.1045711.n5.nabble.com/T5-ValidationException-from-validate-event-leads-to-ERROR-level-logger-statement-tp4860047p5654429.html Sent from the Tapestry - User 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
