Thank you for your response! But I think it is a bad idea to keep a version in every DTO object. How we will address issues if one of the service URLs was changed (DTOs are not changed, but service moved from /service to /new-service)?
I've heard about the solution based on cookies. We can set cookies from server-side that will keep a version that is used now on server-side. GWT Client application will check that server-side version cookie and client-side ones are same, if they aren't - the application should be reloaded. I think that cookie-based solution will fix the problem, but it's unbelievable that GWT developers didn't address the reload problem. -- Kind regards, Ignat Alexeyenko. On Mon, Dec 14, 2009 at 3:05 PM, Nicanor Cristian <nicanor.bab...@gmail.com>wrote: > I did the following: > My DTO's have a field that contains the version of the client-side app. > Server-side I also have the client-side version number. If on serverside > arrives a DTO having other version than the one in the config file, than > I send to the client an error code that the client-side error handling > logic will reload the page. > Seems pretty standard. > > On 12/13/2009 05:04 PM, Ignat Alexeyenko wrote: > > Sirs and Madams, > > The Great GWT Masters! > > > > I want to ask - if there is any way to reload GWT application in > > browser if new version was deployed? > > > > Please, consider the following scenario: > > 1. User Logins in GWT application. > > 2. During user work new version of the application was deployed on > > server. User doesn't close his browser. > > 3. When user tries to do something in GWT application he will see the > > StatusCodeException - because browser is running old version and > > ServerSide generates responces based on new code base. > > > > Is there is STANDARD way or common pattern to define at step 3 that > > the GWT app in client-side is out-of-date and should be reloaded. > > > > -- > > Kind regards, > > Ignat Alexeyenko. > > > > -- > > > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > > To post to this group, send email to google-web-toolkit@googlegroups.com > . > > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > > > > > > > > -- > > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
