No. You have to track the changes yourself. Or use Page as the scope. What's the reason to put values in session anyway?
-Matej On Wed, Dec 10, 2008 at 11:18 PM, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote: > Dear community, > > I'm facing with a really ugly problem. In my web app I need to store some > variables in the Wicket session. > > But this cause some nasty side-effects when users click on the browser back > button. > > The page displays the previous content correctly but some components, which > model is based on session values, do not. > > Is there any best practice for Wicket session to support the browser back > button (so that coming back the session is restored to the previous state)? > > Thank you, > > Paolo > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
