Have a google for checked exceptions vs RuntimeExceptions, there are loads of resources out there where this argument is played out. Also, reading the Spring documentation will help explain (Rod Johnson is keen on the no checked exceptions technique).
A whole new debate could be played over again, so it is best to read some of the other 'flame wars' on the topic that already exist. I guess the big thing was in the past, everyone would catch a checked exception, and then rethrow some othe checked exception. I mean, there often isn't much you can do about an SQLError, so, why force every single part of your program to have a million catch blocks, all of which just catch and rethrow the same exception. Why not just have one or two points that really make sense to do exception handling, and have them handle a runtime error.
To me, that's the basic idea.
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads