> you shouldnt be calling setresponsepage inside constructors > try RestartResponseException
Yes, RestartResponseException forced it to response fine. Anyway, it's a shame "setResponse" sometimes fails in constructors, I already have other web-flows working fine with it. That's because I have some flow-decision-logic concentrated in constructors (logic-convergence reasons) instead of previous page's end-points (links, buttons, etc). May should I extract that constructors logic-convergence to be processed appart in a "Switch" class that may accept a WebPage parameter to then internally call its "setResponse", so avoid logic in constructors and then call this "Switch" class at the end-points. I guess that maybe this will not be applicable in all cases, but could try. ------------------------------------------------------------------------- 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
