> > Is there an elegant solution to handle when a new release is > > deployed while you are in the GWT app?
I thought through some of this awhile ago: http://draconianoverlord.com/2010/07/07/gwt-seamless-upgrades.html > IncompatibleRemoteServiceException for GWT-RPC for instance, which is used > here in Groups, or other means) Interesting. It looks like Groups doesn't use type name elision? I see some FQCNs like java.util.List, but not as many FQCNs as in our non-type-name-elided messages. Makes me wonder if Google shares serialization policy files cross builds? This seemed kinda tricky to setup in an intelligent way (would want to ignore CI/non-production serilalization files, wouldn't want to keep them forever, etc.), so currently I don't share policy files across builds. Which means I can't use type name elision (well, without more forced refreshes, vs. when-they-feel-like-it refreshes). - Stephen -- 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.
