Guys, guys, did you read my reply? I fixed this and you can now use setResponsePage in your constructor or anywhere you want!. I just made this issue http://issues.apache.org/jira/browse/WICKET-298 so that the change will be in the change log.
Eelco On 2/19/07, manu <[EMAIL PROTECTED]> wrote: > > > > available, and I cannot think of a good end-user reason why this > > > > couldn't be called. The getMarkupId method can in fact be called in > > > if it is possible to make every method work at constructor, of course > > > this is not necessary. > > It's a good idea to shield people from errors that aren't immediately > > clear until runtime. > > Instead of that, wouldnt it be easier to make "setResponse" work > forcibly in construction time similar as "RestartResponseException" > does when explicity called? cancelling current page creation (& its > component-tree) and force flow to the new page before responding... > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
