I recently had an issue with the LoginPage also. This was using the AuthenticatedWebSession and AuthenticatedWebApplication classes. Not sure if this holds true with Wasp.
I wanted to access the page parameters in the LogIn class itself but could not. I had to save the page parameters in the web session that was just created via the Request object and pull them in from the session in the LogIn class. I assume in your log out method that the session is being invalidated. When the new log in page is displayed, a new session may be there. Check during the constructor phase of your web session and see if the Request object has the page parameters you desire. Not sure if they will be, but worth a shot. -----Original Message----- From: glory [mailto:[email protected]] Sent: Monday, June 15, 2009 10:47 PM To: [email protected] Subject: Send Page Parameter to Login Page after Calling Logoff Method Hi, wicket users! Is there any way to send a page parameter to the login page after calling logoff() method in a logout page? ((WaspSession)Session.get()).logoff(new LoginContext()); PageParameters parameters = new PageParameters(); parameters.put("myParameter", myParameter); setResponsePage(LoginPage.class, parameters); I've tried it so many times, I got no idea how to get the parameter. Does anyone have idea? Thanks in Advance, Glo _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ EMAIL CONFIDENTIALITY NOTICE This Email message, and any attachments, may contain confidential patient health information that is legally protected. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party unless required to do so by law or regulation and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or action taken in reliance on the contents of this message is strictly prohibited. If you have received this information in error, please notify the sender immediately by replying to this message and delete the message from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
