These are useful tips, but how do you get that transient parameter into the page to begin with unless you copy it to a property value?
onActivate is not called for component initialisation so doesn't help with respect to copying the parameter value. ----- Original Message ----- From: Lance Java To: Tapestry users Sent: Monday, December 02, 2013 9:27 AM Subject: Re: component paramter frustrations I avoid session usage at all costs (with the exception to the rule being the logged in userId) Why not pass the parameter values in your events so the app is stateless? Also, remember that page. onActivate(...) is called for page render and ajax events so sometimes it's better to initialise here instead of @SetupRender.
