Re: Access to AsyncFragmentLoader$HttpDownloadFailure

2011-08-30 Thread Stephen Buergler
Is it a good idea to post to really old threads? Anyway, I see that if there is a 404 error the exception thrown is now IncompatibleRemoteServiceException. so VladS's original concern is taken care of. I still think it would be a good idea to make HttpDownloadFailure a public class though, because

Re: Access to AsyncFragmentLoader$HttpDownloadFailure

2010-02-07 Thread Sky
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 wrote: > We are using GWT.runAsync to load part of our our application. > > The application may run in the client

Access to AsyncFragmentLoader$HttpDownloadFailure

2010-02-07 Thread Vlad Skarzhevskyy
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: