On Wed, Oct 6, 2010 at 10:38 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
> Wrong.  First, you have to understand what is happening behind the scenes.
>  Look at the URL that actually appears in your form's "action" attribute -
> it is a full URL to a specific component, which will invoke the
> IFormSubmitListener on that component (i.e.
> ../?wicket:interface=:13:loginForm::IFormSubmitListener::).  After that form
> is done processing, you are redirected to a URL to render whatever page is
> supposed to be rendered.  If you haven't specifically called
> "setResponsePage(...)", then this means that Wicket hast re-render the page
> that your form was on.  BUT - it can't send you back to a bookmarkable URL
> for that page (your pretty mount with query string parameters, etc), because
> your form submission could have changed all kinds of state on the page, and
> sending you to a bookmarkable URL will result in your page constructor
> getting called and rendering a new page (without all of those state
> changes).  So, you must be redirected to the exact version of the page that
> your form just modified.  Thus, you are redirected to something like
> http://localhost:8080/?wicket:interface=:13:1::: - which is a URL, not for
> the form, but for the specific version of the page that should be rendered.

We should copy/paste this into a Wiki page or something, Jeremy.
Thanks for taking the time to explain this in-depth for folks.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to