I had the same problem when moving to 5.0.16. It was pretty simple for me, since what I was doing was initializing my persistant variables in the declaration. What I did was move the initialization to the SetupRender phase of the cycle.
Hope that works for you too. Cheers, Marcel Eric Ma wrote: > > Why was this restriction introduced in 5.0.16? It completely breaks our > application. If the benefit is marginal, can we roll back to the original > behavior? Or alternatively, what is a "better" practice under 5.0.16? > > Thanks, > -- View this message in context: http://www.nabble.com/-T5--Persistent-fields-may-not-be-updated-until-after-the-page-has-finished-loading-tp20587662p20606832.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]
