On 4/22/08, Kevin C. Dorff <[EMAIL PROTECTED]> wrote: > NOW, to help with some future questions: With T3/T4 it was pretty easy to > determine what methods to use for what, just look at the objects I was > extending or implementing and I could see what method to implement or > override to get what functionality. But since T5 uses POJO's, I am left > trying to discover methods like > > onSubmit > onValidateForm > onValidateFromPassword > onSelectedFromResetButton
You can use the @OnEvent(component = "componentName", value="eventName") annotation (http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/annotations/OnEvent.html) instead of method name conventions and then you can name your method any way suits you best. I prefer this than using name conventions, as a single typo and a name convention fails. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
