I used to use onActivate to do initialization but I also switched to setupRender. I also think onActivate is called when rendering links and if for example you put a database query in it you'll do more queries than you need.
However in this case I would not use either I'd use @ActivationRequestParameter for the search parameters and do what Thiago said "I usually don't fetch the data for it in onActivate() or setupRender(), but in a property which is passed directly to the source parameter" The problem with @Persist is if you leave the page and come back your parameters will still be there. In most cases that's not what a user expects. It also puts stuff in the session where request parameters are in the url. That's always a plus to me. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Grid-is-empty-after-inPlaceUpdate-tp5585265p5586879.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
