My sign in panel does this in its onSubmit():

if (signIn(getUsername(), getPassword(), shouldRememberMe())) {
        if (!continueToOriginalDestination()) {
        
setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(
                                getApplication().getHomePage(), 
(PageParameters) null));
        }
}
else {
        error(getLocalizer().getString("signInFailed", this, "Sign in failed"));
}

This works great.  Now I was trying to add some checks against the browser
using the ClientInfo data that is already collected, but "cookiesEnabled"
only gets set through the "ExtendedBrowserInfo".  However, when I do this in
Application.init():

getRequestCycleSettings().setGatherExtendedBrowserInfo(true);

The continueToOriginalDestination() does not return the correct value.  I
think it has something to do with the way that extended info is gathered
(something about posting data to the BrowserInfoPage) that it loses my
original destination.

Does this seem to be accurate?  If so, how can I overcome this problem?  If
I get an extra minute I'll try to put together a quickstart but I was hoping
that if one of you was familiar with the BrowserInfoPage and its functioning
that you might be able to give me a headstart.

Chuck
-- 
View this message in context: 
http://www.nabble.com/quirk-with-getRequestCycleSettings%28%29.setGatherExtendedBrowserInfo%28true%29-tf3176153.html#a8812387
Sent from the Wicket - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to