uncaught-exception

I am trying to retrieve data in a JSON object (which I have validated is correctly formatted) and output the data into the firebug console. I validated the JSON using JSONLint (http://jsonlint.com/) and know the data is not returning in JSON object because when I log it, it is logging as text rather than an object. When I look at the ajax post, there is a JSON tab and it shows the object, I just cannot retrieve it for some reason. My ajax call is $.ajax({ url:'/coords/base', data: { type: obj.type, id: obj.id }, dataType:'text', type:'get', async:false, success: function(data) { console.log

This question may sound a little silly ;) How would approach the possibility of an uncaught exception within the UncaughtExceptionHandler ? Well, you have to catch them yourself. The documentation of uncaughtException() linked by you states this clearly: Any exception thrown by this method will be ignored by the Java Virtual Machine. But you can only plan so far. So you handle the exceptions of your exception handler but who handles that code? It's the same with logging a failed logging event. Exception handlers all the way down... Farmor Very interesting question, I haven't thought about this

Is there a standard way to catch uncaught exceptions that happen inside of a java servlet container like tomcat or Jetty? We run a lot of servlets that come from libraries so we cannot easily put our on try/catch code. It would also be nice to in as generic of a way as possible catch and log all uncaught exceptions in our web application (which runs in Jetty) to our bug tracker via the API provided. Please not I need to log the exceptions only, whether a a redirect is issues to a custom error page will not help me. We do everything via GWT-RPC so the user would never see an error page. I think

After reading some excellent posts about the difference between AppDomain.UnhandledException and Application.DispatcherUnhandledException, it appears that I should be handling both. This is because it is significantly more likely the user can recover from an exception thrown by the main UI thread (i.e., Application.DispatcherUnhandledException). Correct? Also, should I also give the user a chance to continue the program for both, or just the Application.DispatcherUnhandledException? Example code below handles both AppDomain.UnhandledException and Application.DispatcherUnhandledException, and