You seem to be having a caching problem: reloading the page should be made
to revalidate the page (*.html and *.nocache.js) freshness to the server, so
that the under construction (you're using a 503 Temporarily Unavailable,
right?) page and then the new version are correctly loaded back from
Hi,
when I install a new server version, I redirect my URL to a under
construction page beforehand. Then I undeploy the app and redeploy
it.
However, during this process the clients often still have the old app
in their browsers. When the new app is deployed they may receive
incompatible errors.
You need to handle IncompatibleRemoteServiceException
Read
here:
http://code.google.com/webtoolkit/doc/1.6/DevGuideServerCommunication.html#DevGuideHandlingExceptions
Regards,
Nirmal
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To
When you call to your services you can do something like this in your
AsyncCallback
public void onFailure(Throwable caught) {
if (caught instanceof IncompatibleRemoteServiceException) {
Window.Location.assign(/newUrl);
}
}
Regards.
On 4 ene, 09:22, Nirmal Patel
