On Fri, May 18, 2012 at 4:12 PM, armhold <[email protected]> wrote: > Ajax calls do save the page state. I think the real issue for you is > that if users have the page open but idle for a long time (longer than > session expiration... 30 mins?) the Ajax links won't work for them > when they decide to start using the page again.
If the page is mounted with #mountPage()/MountedMapper then clicking on an AjaxLink that leads to an expired page will create a new instance of the same type and will *not* execute #onClick() for that link (because the link is gone with the first page). But the user will be able to proceed with his work. > > You could perhaps use a AjaxSelfUpdatingTimerBehavior to keep the > session open, if you can afford to have a session running for every > user with an open tab. > >> Since the users will stay on a single page for a long time, and >> never go to a different page, do I need to be concerned with wicket >> not saving/serializing the page state? > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Single-page-wicket-app-tp4634756p4644559.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
