Spot on. When you press Reload, you're just reloading the HTML host page and reloading the JS. This is a challenge with all JS apps. Fortunately, GWT solves it well with the History object and the various MVP frameworks (including Activities and Places in GWT 2.1) make it even easier.
http://code.google.com/webtoolkit/doc/trunk/DevGuideMvpActivitiesAndPlaces.html -- David Chandler Developer Programs Engineer, GWT On Oct 15, 7:53 am, salk31 <[email protected]> wrote: > Have you looked at the History class? GWT gets around the problem you > are talking about by using #foo stuck on the end of the URL (so will > work for reload and browser history). > > http://code.google.com/webtoolkit/doc/latest/DevGuideCodingBasicsHist... > > Works really nicely. I've not played with it yet but higher level > support in 2.1 > > On Oct 15, 8:32 am, Vibhuti Gupta <[email protected]> wrote: > > > > > Hi > > > When I refresh any page in my GWT application it loads the login page as the > > browser URL does not change. Also clicking back button of the browser loads > > the login page. I need a way to load the page i am currently on when user > > refreshes the page instead of login page getting loaded. > > > Anyone has any ideas how to achieve it. > > > Thanks -- 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.
