On 6/25/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> instead of setResponsePage(SetStatePage.class) do throw new
> RestartResponseException(SetStatePage.class)
That's the workaround for Wicket 1.2. Note that in Wicket 1.3 you
should be able to set the response page in the constructor. Also note
that this might not actually be better; not having to use the
exception imho looks better, but the advantage of using the exception
is that the rest of the page you have that statement in won't be build
up (and since you are not rendering it, why would you want to do that
anyway?).
Eelco
if you do call setResponsePage() from another page's constructor do you end
up with both of them in the pagemap? With the exception you will only end up
with one, not sure about the other way around. if you do end up with both we
should prob fix that somehow as the other page is not reachable?
-igor
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
