If you're using Tomcat, Tomcat 7 supports updating a webapp and keeping the old instance running along side it for situations like this. As I understand it (I don't use it yet), http sessions/requests tied to the old webapp get routed to the old instance and new sessions get routed to the newly deployed one. After all the sessions are dead from the old web app it's undeployed. Obviously, this won't work for everyone since some people have issues hot deploying their app, but it's something you could look into.
On Jan 5, 7:39 am, Kyle Baley <k...@baley.org> wrote: > Now that I've determined our problem, I have another question. Is there a > clean way to *not* require the user to refresh the page? -- 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. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
