Hi, I'm using the login/authorization strategy taken from the wicket examples, which is throw new RestartResponseAtInterceptPageException(SignIn.class);
in the application class and calling continueToOriginalDestination() in the login page. However when I'm using a bookmarkable page with PageParameters, the parameters get lost in the process.. Am I missing something, or is this behaviour just not supported? Regards, Wouter ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
