On 9/22/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Why are you using setRedirect directly like that btw? > > So you want to block the login page after a user authenticated? Why > not just block the page for authenticated users e.g. with an > authorization strategy. Or maybe even better... in the submit method > of your login form, before you do anything, check whether the user was > authenticated, and if so, just ignore the whole action and redirect > him to e.g. the home page. One thing I'm curious about is why you > would design your application in such a way that a re-login is a > problem in the first place?
Forget about the fact that this happens to be a SignUp page. It is a generic problem that applies to all kinds of forms. S. ------------------------------------------------------------------------- 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
