Handling AsyncCallFail

[Shawn Johnson]

I am trying to gracefully handle AsyncCallFail after an application update.  The latest test I tried, I call Window.alert() - giving an "Oops.." type of message.  The AsyncCallFailEvent occurred on an attempt to navigate the application after the initial application was loaded in the browser, and the user clicked on a new 'page' - that page's code wasn't yet loaded.  After I clicked the OK form the alert box, the application became un-clickable?   Is there a best practice or any advice on handling this kind of situation?

[Jonas]

Handling hot deploys is always a tricky issue. A solution that I find works best is to simply show a message to the user that the application needs to reload, and then force a redirect to the main page which will download the new Javascript. Google groups is using a similar soluition. If you leave your browser open for the night and come back you'll get a small message that it needs to reload.

[Shawn Johnson]

Thanks for the reply.

How about differentiating between a network hiccup and a hot deployment, on the client?

On Jun 4, 2013 6:39 AM, "Jonas" <sar...@gmail.com> wrote:

Handling hot deploys is always a tricky issue. A solution that I find works best is to simply show a message to the user that the application needs to reload, and then force a redirect to the main page which will download the new Javascript. Google groups is using a similar soluition. If you leave your browser open for the night and come back you'll get a small message that it needs to reload.

--
You received this message because you are subscribed to a topic in the Google Groups "GWTP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gwt-platform/3ipBcv16KtI/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to gwt-platform...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jonas]

You will need to make a custom exception that you throw to the client side.

For example, if you are using RPC and perform a hot deploy you most often get a IncompatibleRemoteServiceException thrown on the backend. What I do is have a HotDeployException that extends from GWTP's ActionException that I throw instead which due to ActionException and the dispatcher propagates back up to the client. You can then inspect the exception on the client and act accordingly.

In case of network hiccups, you would probably get some kind of RuntimeException that you need to handle.

[Heiko Braun]

sounds like you need to unlock the place manager. I think there was a mail form Harald about that a while ago. see also:

https://github.com/hal/core/blob/10c8b08e9b2098a771afefed4f13b234f68f0505/gui/src/main/java/org/jboss/as/console/client/core/AsyncCallHandler.java

Regards, Heiko

[Harald Pehl]

I sent a pull request at that time to address the issue :https://github.com/ArcBees/GWTP/pull/196. Though I don't know if the fix is already in the current version. 

See this thread for further infos: https://groups.google.com/forum/#!topic/gwt-platform/3VDf-eHzBi0

- Harald