I second this motion. In my opinion you provide a solid argument. Hopefully the GWT dev team will agree and see fit to make that exception public.
On Feb 7, 2:16 pm, Vlad Skarzhevskyy <skarzhevs...@gmail.com> wrote: > We are using GWT.runAsync to load part of our our application. > > The application may run in the client Browser for some time before it would > need to open the unloaded fragments. > If during this time the application on server is updated e.g. GWT recompiled > and deployed we may get exception on client: > ---- > com.google.gwt.core.client.impl.AsyncFragmentLoader$HttpDownloadFailure: > HTTP download failed with status 404 > ---- > > In RunAsyncCallback.onFailure(Throwable) we can analyze the reason for > error. If it is status 404 then we can show error: > "We updated our application. Reload Yes/No? " and call > Window.Location.reload(); to gracefully recover from this error. > > But the Exception HttpDownloadFailure is private static class inside gwt > AsyncFragmentLoader implementation. > Does it make sense to expose the HttpDownloadFailure exception so that > application would be able gracefully and properly recover from some known > errors? > > BTW the StatusCodeException with nearly the same meaning is public in RPC > package com.google.gwt.user.client.rpc. > > Vlad > > PS > For now I'm just looking for the string "HTTP download failed with status > 404" in Throwable message to recover from this errors. -- 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.
