Re: Continuous Delivery with GWT

We accomplish this with context naming (http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#naming) and GWT.setUncaughtExceptionHandler(new OurExceptionHandler()).  When the ExceptionHandler is notified of an exception that is an instanceof  IncompatibleRemoteServiceException we call Window.Location.reload();  I redeploy new versions / fixes regularly during production hours.

This works 99% of the time.  I think there are other possible excpetions from new wars but have not tracked them all down.

On Monday, August 11, 2014 12:59:31 PM UTC-7, Tony BenBrahim wrote:

Has anyone successfully implemented Continuous Delivery with GWT. The biggest obstacle I see is GWT RPC, that seems to check that the client version matches the server version, so that when a new version of a backend is deployed, users will get an error message about an incorrect version and be asked to refresh the browser. I will look at disabling this check, but if it is not possible or has negative consequences, may have to switch to REST+JSON from GWT RPC? Anyone tried this successfully?

Thanks in advance

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.