You could use pageAttached http://tapestry.apache.org/tapestry5/tapestry-core/guide/lifecycle.html
2008/11/8 Joel Halbert <[EMAIL PROTECTED]> > just realised that the order of invocation of onActivate methods is the > other way around to that which i thought it was: > http://markmail.org/message/7o52hrmcvli3jsje > > This does pose the question though: how can I invoke base functionality > after subclasses have been initialised, but before PageRender? > > hmmm (being Saturday I've very likely missed something here) > > On Sat, 2008-11-08 at 14:40 +0000, Joel Halbert wrote: > > Hi, > > > > Is it possible to use an annotation to define which method should be > > used to set the page activation context? > > i.e. I would like to define an onActivate() method, but have it called > > something else, e.g. onActivateX(). > > > > A reason for wanting to do so is to ensure that i may have a single > > onActivate method in a base class which is always called regardless of > > wether there are onActivate methods in subclasses (that might otherwise > > override it and not call super.onActivate()). > > > > Thx > > Joel > > > > > > > -- > SU3 Analytics Ltd > The Print House > 18 Ashwin Street > E8 3DL > London > > Tel: +44 (0) 20 3051 8637 > Fax: +44 (0) 20 8196 2215 > Mob: +44 (0) 79 7431 0685 > www.su3analytics.com > > SU3 Analytics Ltd is a company registered in England and Wales under > company number 06639473 at registered address 61b Oxford Gardens, London > W10 5UJ, United Kingdom. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
