Thank you for your responses, this clarifies my way
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-4-How-to-discard-persistent-fields-when-the-user-leaves-a-page-tp3318549p3321092.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Right, the trick is calling discardPersistentFieldChanges() at the
right time. You cannot, or at least it doesn't make sense in the
general case, to simply call it on browser's onunload().
Tapestry-conversations module relies on the idea of short term
expiration of page-specific session data, where
discardPersistentFieldChanges() will discard @Persist values, but the
original question was how to do it when the user leaves the page.
Read Howard's message here along with the following messages:
http://markmail.org/message/67dbxuwf3rw3naja
In a nutshell, it was easy to implement pageReset, but
It's called discardPersistentFieldChanges:
http://tapestry.1045711.n5.nabble.com/T5-Cleaning-page-s-persistent-field-td2419355.html
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-2-4-How-to-discard-persistent-fields-when-the-user-leaves-a-page-tp5867260p5869215.html
Perhaps you already evaluated, but decided against using
tapestry-conversations for one reason or another, but just in case you
haven't, see http://tynamo.org/tapestry-conversations+guide.
(I really don't want to advertise repeatedly, but at the same time I
frequently hear people saying they didn'
Hello appreciate members
Anyone knows a way to discard persistent fields (delete fields of the
session) of a page when the user leaves it and changes to another ?
Thanks in advance
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-4-How-to-discard-persistent-fields-w
