Comments on: Don’t throw exceptions from a static initializer http://javablog.co.uk/2007/07/02/dont-throw-exceptions-from-a-static-initializer/ by Java coders, for Java coders Thu, 22 Jul 2010 12:24:38 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Anjan Bacchu http://javablog.co.uk/2007/07/02/dont-throw-exceptions-from-a-static-initializer/comment-page-1/#comment-69 Anjan Bacchu Mon, 02 Jul 2007 23:43:50 +0000 http://javablog.co.uk/2007/07/02/dont-throw-exceptions-from-a-static-initializer/#comment-69 <p>I've been burnt with this issue. Yes, the exception was lost and subsequent class references giving NCDFE Errors were really painfull to understand.</p> <p>Only after remote debugging, was I able to figure out what happened.</p> <p>Then again, exceptions should be easily filterable so that you can narrow down to a particular Java class if you are in a DEBUG mode. Since we had a huge amount of stdout and exception trace in our log file, I could NOT easily find out what was happening.</p> I’ve been burnt with this issue. Yes, the exception was lost and subsequent class references giving NCDFE Errors were really painfull to understand.

Only after remote debugging, was I able to figure out what happened.

Then again, exceptions should be easily filterable so that you can narrow down to a particular Java class if you are in a DEBUG mode. Since we had a huge amount of stdout and exception trace in our log file, I could NOT easily find out what was happening.

]]> By: Ricky http://javablog.co.uk/2007/07/02/dont-throw-exceptions-from-a-static-initializer/comment-page-1/#comment-68 Ricky Mon, 02 Jul 2007 21:04:14 +0000 http://javablog.co.uk/2007/07/02/dont-throw-exceptions-from-a-static-initializer/#comment-68 <p>Perhaps the class depends on some condition so strongly that it makes no sense to let classloading complete normally.</p> <p>I just tested this out (Java 6), and it seems that the resulting stack trace is quite readable (I wondered whether your lost hours were down to the exception being swallowed).</p> Perhaps the class depends on some condition so strongly that it makes no sense to let classloading complete normally.

I just tested this out (Java 6), and it seems that the resulting stack trace is quite readable (I wondered whether your lost hours were down to the exception being swallowed).

]]>