On 2/19/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > sure, but does it abort the page or do you end up with an extra page in the > pagemap?
No, it doesn't abort the request. If you want to do that you need to use that exception. So while it typically doesn't make sense to call setResponsePage in a constructor, it is not *wrong* nor should Wicket - like we did - ignore it altogether. Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
