Sounds like when your entry point loads (that happens on refresh) it needs to check if the user is logged in (check a cookie or make an AJAX request to the server) and then display the appropriate widgets (view).
However, I suggest that you make the login page a separate page from the page that loads your GWT application. When the user tries to access your GWT application and is not logged in, redirect the browser to the login page. After the user successfully authenticates, redirect the browser to your GWT application. This approach avoids the problem you are having, and it prevents the user from being able to download your GWT application (JavaScript code) when they don't have access. -Richard On Jun 10, 1:31 am, CIAO <[email protected]> wrote: > Hi I am a newbie to GWT and am working on an application Dev that has > a login page and when the user successfully identifies itself it goes > to a data page (loads the new data widgets after removing the login > widgets) that shows it all the data s/he requires > the problem i am facing is > whenever i press the refresh button (or F5) it goes back to the login > widgets.. > i need to arrest this behavior and user should *NOT* be sent back once > user has logged in... > > thanks in advance > CIAO -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
