you need to store a bookmarkable url that the user should be
redirected to. then your pageexpirederrorpage can check for that url
and redirect to it instead.
since the session is gone you cant store the url there, so i would
suggest storing it in a cookie.
-igor
On Wed, Nov 5, 2008 at 6:03 PM,
thanks for your response.
but... why is this handled differently (trying to call some ajax) than
requesting a regular page ? (like a bookmarkable page). i don't think wicket
internally uses cookies to redirect on continuetooriginaldestination. i
might be wrong.
i mean, if the user is on a page,
that only works for normal requests because the requested url is the
one from browser's address bar. when you issue an ajax request wicket
doesnt know what url is in browser's address bar, it only knows the
non-bookmarkable ajax url that was invoked.
-igor
On Thu, Nov 6, 2008 at 8:33 AM, Cristi
o, i figured wicket also keeps the page from where the ajax call was
initiated somewhere. that's why i thought i was just doing something wrong
that i didn't get anything useful in page expired. sorry, i should first
check wicket code before wasting somebody's time.
thank you very much,
Hello,
Consider a user who is on a modal window and his session expires. When he
tries to do something he will be redirected to the page expired page.
Is it possible that after he logs in to be redirected to the page from where
he opened the modal window? Something like what
