I'm having a hard time understanding what happens when setResponsePage()
is called while processing an Ajax request. Does Wicket:
1. Render the response page's HTML send it back through the Ajax
connection?
2. Tell the browser to make a new request (i.e., redirect) to the new
page?
3.
Take a look at WebPageRenderer#respond(): Inside Ajax requests it
responds with a redirect, which is then analyzed and performed by
wicket-ajax.js in the browser.
Sven
On 02/01/2012 09:43 PM, Richard W. Adams wrote:
I'm having a hard time understanding what happens when setResponsePage()
is
