When an unexpected error occurs on the client side, such as a NullPointerException, the result is that an UmbrellaException is thrown and that generally ends up being interpreted as a javascript error by the browser. Those javascript errors are usually less than helpful in determining what the actual problem was. Does anyone have any suggestions on how to handle the case of unexpected errors?
Can you put a try catch block at the top level of you app as kind of a catch all? If so, what should be done with these exceptions? Should they be sent back to the server to be logged somehow? If not, how can you try to provide some useful information to help with the debugging process? -TJ -- 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.
