I wonder if we could write a code analysis tool that would check for these sorts of things. We have @deprecated for methods and variables, so that works, but when the "adaptive API" changes, it's considerably harder to catch/see. Maybe a find-bugs extension for tapestry upgrades or something?
Robert On Dec 1, 2011, at 12/15:38 PM , Martin Strand wrote: > On Fri, 02 Dec 2011 00:21:09 +0100, angelochen <angelochen...@yahoo.com.hk> > wrote: > >> hi, >> >> to uprade to 5.3, we need to replace all onValidateForm to onValidate, but >> does onValidate works in 5.2.6? > > Yes, the "validate" event works in Tapestry 5.2.6: > http://tapestry.apache.org/5.2/apidocs/org/apache/tapestry5/EventConstants.html#VALIDATE > > "validateForm" was deprecated in 5.2: > http://tapestry.apache.org/5.2/apidocs/org/apache/tapestry5/EventConstants.html#VALIDATE_FORM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
