Comments on: The anti-pattern series: Exception-Handling

By: Richard Relos

Richard Relos — Tue, 16 May 2006 00:19:33 +0000

as these are antipatterns, it would naturally tell us to “do everything else, except these”

>> catch and throw… if catch, you might want to do some processing. meaning, if you catch, you’re taking the exception for yourself. otherwise, don’t catch it at all (and by defining a throws clause)

>> catch, log, and throw… think of the “log” as one of the activities in the catch. just like the rule above, don’t catch then throw.

>> catch and handle… don’t quite get what you mean by this.

cheers

if you need a book, i can recommend some

By: hip2b2

hip2b2 — Mon, 15 May 2006 00:54:02 +0000

I am pretty rusty with my Java having learned it in the Java 1.0 days (early 1997). My idea of J2EE is ATG Dynamo which I learned in early 1999. So, I am pretty out of date.

What does the good book recommend we use if we can’t catch and throw? catch, log and throw? catch and handle?

Thanks!

By: Tom

Tom — Fri, 12 May 2006 19:06:56 +0000

That link I put on “take on exceptions” above is really hard to see. As a form of confession, I need to improve my link color, too.

By: Tom

Tom — Fri, 12 May 2006 19:04:40 +0000

Here's my (partial) take on exceptions. It tries to strike at some of the causes of why people easily use exceptions incorrectly in Java. A different part I need to cover some time is what should be done with the "throws" clause on method signatures.