Comments on: How not to handle exceptions from static code block in Java http://twasink.net/2006/07/07/how-not-to-handle-exceptions-from-static-code-block-in-java/ Robert's Rambling Ruminations Regarding Reality... Thu, 12 Apr 2012 16:31:52 +0000 hourly 1 http://wordpress.com/ By: Robert http://twasink.net/2006/07/07/how-not-to-handle-exceptions-from-static-code-block-in-java/#comment-367 Wed, 12 Jul 2006 23:05:06 +0000 http://twasink.net/wp/?p=199#comment-367 Henry, you are wrong… not about the ExceptionInInitialzerError, which is merely the way the exception gets passed back, but because of the effect the exception has on the class definition. The NoClassDefFoundError which occurs on subsequent access to the class will drown that original exception.

And you _can_ catch Errors. If you weren’t allowed to catch them, they wouldn’t descend from Throwable. There are many situations where you do want to deal with Errors – I’m sure if you stop to think of them, you will.

]]> By: Henry http://twasink.net/2006/07/07/how-not-to-handle-exceptions-from-static-code-block-in-java/#comment-366 Wed, 12 Jul 2006 22:52:05 +0000 http://twasink.net/wp/?p=199#comment-366 Wrong, both of you.

It’s perfectly fine to throw a RuntimeException in a static initializer, because the JVM will catch it and rethrow a java.lang.ExceptionInInitializerError, which is an Error and hence should not be caught.

]]>