On Wed, Oct 29, 2008 at 6:43 AM, Antony Stubbs <[EMAIL PROTECTED]> wrote:
> With RENDER_TO_REDIRECT on, why does this: ^ this pattern implements the redirect-after-post like pattern > http://localhost:8080/non-gizmo-wicket-portlet-events/eventa/?wicket:interface=:11:basic-link:6:ILinkListener:: > redirect to > http://localhost:8080/non-gizmo-wicket-portlet-events/eventa/?wicket:interface=:11:6::: the top url invokes the onclick of a link, after it is processed we redirect to a view url. this is so if the user presses refresh the onclick is not invoked again. like redirect-after-post but actually redirect-after-get for gets that cause actions on the serverside. > while > http://localhost:8080/non-gizmo-wicket-portlet-events/eventa/ > doesn't redirect at all, and the browser points to:? > http://localhost:8080/non-gizmo-wicket-portlet-events/eventa/ > Shouldn't you get:? > http://localhost:8080/non-gizmo-wicket-portlet-events/eventa/?wicket:interface=:0:::: we do not redirect bookmarkable urls. we want a new instance created if the user presses refresh. if you were to invoke any action on that page then you would be redirected to ?wicket:interface=:0:::: also we cannot redirect because the url has to be bookmarkable, eg user actually being able to bookmark it in the browser. if we always redirected to a stateful url that wouldnt work very well :) -igor
