I don't know of an extensive all-in-one-place list, but the documentation is full of information about them all-- if you know where to look :-)
For Form related events, you're most likely interested in validating input: http://tapestry.apache.org/tapestry5/tapestry-core/guide/validation.html -- includes a detailed breakdown of what happens under the Form component heading Other components that trigger events usually specify the event name they trigger in their JavaDocs, if not on their component reference pages. For page related phases, you may want to check out the Page Lifecycle page: http://tapestry.apache.org/tapestry5/tapestry-core/guide/lifecycle.html -- at the bottom mentions 3 possible methods For component related phases, you will want to see the Component Rendering page: http://tapestry.apache.org/tapestry5/tapestry-core/guide/rendering.html Peter Beshai On Tue, Apr 22, 2008 at 11:02 AM, Kevin C. Dorff <[EMAIL PROTECTED]> wrote: > > Thanks for these suggestions. First Robert Zeigler, onValidateForm is > exactly > what I needed, also I found the null-safe comparison was important. > > Second, your suggest about disabling the submit javascript handler was > right > on. The missing piece I put together was that my onValidateForm is always > going to be called but when I added the "onSelectedFromResetButton()" > handler for my reset button, I just did a registrationForm.clearErrors(); > to > clear any errors - as after a reset there shouldn't be any errors. > > 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 > > some of these are intuitive, some are absolutely not. Is there a source > that > just talks about for Pages, Services, Forms, Form Buttons, etc. all the > method names (format of method names) Tapestry will try to evoke, their > order, when, etc? Sometimes it seem that the component reference is > explicit > on this, often (such as onValidate) it seems the component reference > doesn't > mention these at all - or maybe I just am missing something. > > Thanks! Loving Tapestry5 so far (when I am not stumped). > Kevin > -- > View this message in context: > http://www.nabble.com/T5%3A-question-about-onValidate-and-form-reset-tp16809659p16824702.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
