Hi Christoph, no, I have no serialization problems....If you use ajax refresh timer *with high frequency* in pages then PageNumberEvictionStrategy(1) makes your app very unstable...Page is sometimes recreated by framework (*if you redirect to another page*), but without page parameters. So if you're expecting particular page params, you have an app crash...To understand what I'm saying you need to look at PageProvider.resolvePageInstance method, otherwise you can't understand.
Btw, we allow our users to use multiple tabs, but we don't want to remember all pages...So we have 1 page per tab in session, which is ideal state. But with ajax timer you have mentioned problem. I will create ticket in Jira with demo... -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Howto-have-just-currently-viewed-page-in-session-tp4671631p4671639.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
