right, we have implemented the "keep alive timer" as well but still, we also want to handle the ajax expiration exception at client side, because we discovered that we can't preserve the session if the server is restarted
Erik van Oosten wrote: > > Hi Ywtsang, > > Not an answer to your question, but you can also consider using a ajax > timer to keep the session alive. > > For example as outlined in > http://chillenious.wordpress.com/2007/06/19/how-to-create-a-text-area-with-a-heart-beat-with-wicket/. > > Regards, > Erik. > > > ywtsang wrote >> we want to handle session expiration exception triggered by an ajax >> request >> >> since the session is expired, the ajax request can't be forwarded to the >> corresponding ajax behavior, instead, the server throw session expiration >> exception >> (we have configured the handling by >> getApplicationSettings().setPageExpiredErrorPage) >> >> the handling is ok for non-ajax request, but not ajax request >> >> we want to handle that using client side javascript >> >> how can we achieve that? >> >> > > -- > Erik van Oosten > http://day-to-day-stuff.blogspot.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/client-side-handling-of-ajax-request-session-expiration-tp16743324p16762728.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
