My guess would be "onValidateFrom<Form-component-id>" replaces "validateForm" ?
Simply using onValidate is probably not specific enough as it may get triggered by bubbling events. -- Chris On Thu, Oct 27, 2011 at 12:49 PM, <p.stavrini...@albourne.com> wrote: > Hi All, > > The 5.3 release notes provide the following info: > "validateForm" event triggered by Form component (replaced with "validate" > event) > > How validate replaces validateForm is not clear to me and I could not find > any more info? > > These two methods are certainly not interchangeable, i.e.: validateForm was > invoked just before OnSucess and once for a form, whereas onValidate may > potentially be called several times with a different event life-cycle. Is > there an example of how to re-factor code that was using 'validateForm' to > use 'Validate', and in such a way as to reproduce the behaviour of > validateForm? The only other alternative is to have one method per data > point, which is really not practical for anything scalable. > > Kind regards, > Peter > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
