What could cause an UmbrellaException anonymous function on deployed GWT app?

Question

I seem to be running into an odd problem. When using my GWT application in a local environment, everything works as it should. The problem comes in after I compile and deploy my application. When I go through my project workflow and click on a certain link to switch into a new panel, I get the following error (from my console in Chrome):

Uncaught com.google.gwt.event.shared.UmbrellaException: One or more exceptions
caught, see full set in UmbrellaException#getCauses (anonymous function)

This error is thrown by one of the cache file generated by GWT at compile time. But this never happens on the locally deployed program (deployed from Eclipse, "Run as Web Application"). Has anyone ever run into this issue or can provide any direction for a fix?

Thank you! :)

Solution 1

I had the same problem just now. Works locally, fails with the mentioned Javascript console error, nothing in server logs.

Turns out that client Java code (which is complied to Javascript) had try/catch block which worked when executed in Java, but failed silently when compiled to Javascript. I'm still not sure what was the exact nature of the problem, but try removing try/catch blocks.

(It seems that in my case, table.getWidget() call was failing and throwing exception.)

Solution 2

I had the same problem, i think interpretation of try catch is not the same than in Java... after gwt compilation, when you are in catch case, the execution failed. If you open firebug, you can see point of errors into JS.

Solution 3

I had the same problem, it worked in development mode. Then, after I compiled I would get an error. To fix, I had to get rid of:

try{
   //some code
} catch(NullPointerException ex){
   //more code
}

Instead I did:

if(variable != null){
   //some code
} else {
   //more code
}

After that it worked perfectly.

Comments

[Omar Estrella]

Best answer so far. We actually never got down to the root of the problem, but switched our panel transition workflow and that seemed to solve the problem. Thanks!