Pointless discussion!

Checked exceptions are very useful and their handling depends on the kind of product you code is part of: -a library -a desktop application -a server running within some box -an academical exercise

Usually a library must not handle checked exceptions, but declare as thrown by public API. The rare case when they could wrapped into plain RuntimeExcepton is, for example, creating inside of library code some private xml document and parsing it, creating some temporary file and then reading that.

For desktop applications you must start the development of product by creating your own exception handling framework. Using you own framework usually you will wrap a checked exception into some of two to four wrappers (your custom sub-classes of RuntimeExcepion) and handle them by a single Exception Handler.

For servers usually your code will run inside of some framework. If you don't use any (a bare server) create your own framework similar (based on Runtimes) described above.

For academical exercises you can always wrap them directly into RuntimeExcepton. Somebody can create a tiny framework too.

Checked exceptions are very useful and their handling depends on the kind of product you code is part of:

• a library
• a desktop application
• a server running within some box
• an academical exercise

Usually a library must not handle checked exceptions, but declare as thrown by public API. The rare case when they could wrapped into plain RuntimeExcepton is, for example, creating inside of library code some private xml document and parsing it, creating some temporary file and then reading that.

For desktop applications you must start the development of product by creating your own exception handling framework. Using you own framework usually you will wrap a checked exception into some of two to four wrappers (your custom sub-classes of RuntimeExcepion) and handle them by a single Exception Handler.

For servers usually your code will run inside of some framework. If you don't use any (a bare server) create your own framework similar (based on Runtimes) described above.

For academical exercises you can always wrap them directly into RuntimeExcepton. Somebody can create a tiny framework too.