Thanks Johan,
I was a little big unclear. By default the HTML pages returned from wicket has
no-cache, so the back button usually posts request to server. When the previous
page url is RedirectPageRequestTarget, the page instance is found in page map
and rendered again. Why is the
first of all no-cache will not result in a get request to the server again.
That will only happen if you add no-store to the configureResponse param
of the WebPage.
i thought that onRedirect() didn't even get called , dummy method (it
doesn't do anything). But it seems to be called i see.
We
Thanks Johan for your time and support,
I tried to override onBeforeRequest(), just to test - the first call to
onBeforeRender suceeds but any furter call will throw and should redirect to
some page, but the redirect doesn't work. Wicket doesn't do anything special on
AbortException. The
Hi Jan,
Try to throw an RestartResponseAtInterceptPageException.
Erik.
jan_bar schreef:
Thanks Johan for your time and support,
I tried to override onBeforeRequest(), just to test - the first call
to onBeforeRender suceeds but any furter call will throw and should
redirect to some
Thanks Erik and Johan, now I have what I searched for.
Jan
Erik van Oosten [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hi Jan,
Try to throw an RestartResponseAtInterceptPageException.
Erik.
jan_bar schreef:
Thanks Johan for your time and support,
I tried to
When a user presses Back in a browser the page doesn't render again at
least
not in the serverside. By default it is a puur client side thing. (you can
configure
the page in configureResponse to always go back to the server when a user
hits back)
So what gets throwed at what time?
On 12/14/06,
