Tapestry has not way to determine if a value is mutable or immutable. What was happening is that people were assigning mutable values (lists, maps, user-defined objects) as the initial value of a persistent field. The end result was that these mutable objects were being shared between users, as page instances got re-used.
The change forces devs to be aware of this issue and to explicitly assign to it at a time when the value can be persisted in the session. On Wed, Nov 19, 2008 at 11:39 AM, Eric Ma <[EMAIL PROTECTED]> 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-tp20587662p20587662.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] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
