Trends: Is it time to throw out checked exceptions?
Going through school and much of my career I would follow the orthodoxy of using checked exceptions to handle exceptional conditions. While it isn't too difficult to trace down a bug when a school project is only a small collection of 5 to 15 code files, it is an entirely different issue when it comes to enterprise level development. Enterprise applications often have many method calls on the stack, if a method deep in calling hierarchy throws an exception it forces the programmer to either catch and wrap that exception or throw it up to the next level. So you often end up with excessively long stack traces or methods throwing exceptions that are not relevant to their abstraction layer. I'm certainly not experienced enough to be an authority on this issue, but I decided to do some research on the topic and here are couple of really informative articles I found:
http://www.ibm.com/developerworks/java/library/j-jtp05254.html
http://onjava.com/pub/a/onjava/2003/11/19/exceptions.html?page=2
Related posts:
Categories
Tag Cloud
Archives
- November 2009 (3)
- October 2009 (18)
- September 2009 (15)