Is your login page unprotected? On 18 March 2015 at 16:39, Tushar Bhasme <[email protected]> wrote:
> I am trying to handle all the OnFailure case of all the asyncCallback > classes in my application. Basically, if the backend throws some specific > error- like "SessionInvalid". I want the user to be showed the Login > screen. The approach I followed was " > http://stackoverflow.com/questions/3657572/how-to-redirect-to-login-page-after-session-expire-in-gwt-rpc-call". > In my custom callback, I check the error and call revealDefaultPlace (which > is my login page). > > The trick mentioned on stackoverflow seems to work, but in my app, get the > error: "Encountered repeated errors resulting in an infinite loop. Make > sure all users have access to the pages revealed by revealErrorPlace and > revealUnauthorizedPlace. (Note that the default implementations call > revealDefaultPlace); Encountered repeated errors resulting in an infinite > loop. Make sure all users have access to the pages revealed by > revealErrorPlace and revealUnauthorizedPlace. (Note that the default > implementations call revealDefaultPlace)" > > Thanks, > Tushar > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
