I'm quite new to java (learning), but have worked in Visual Basic for a few

After reading through the error handling methods available in java, I'm
wondering how most industrial strength java applications structure error

In VB, I would define a base error number for each class, and then assign
any errors that were raised by the class to that base plus some increment.
This error number could be checked upon an error condition caught within
each method and the appropriate error handler could be launched - or the
code could make some repair or retry operations before failing. System
generated errors are easy to identify (by number range), and can be
processed appropriately too. Errors can be processed by a handler that's
generic within the app too. This kind of structure seemed pretty elegant
and worked ok too.

I'm wondering if the try / catch block methods don't kind of gum up the flow
of code within methods. Also, without the ability to retry the code that
generated the error, or resume on the line immediately after the error - how
do you recover/retry certain operations? By using try/catch blocks around
individual lines or very small blocks of code?

Is there a good reference for real-world error handling in java apps that
anyone can recommend?

Tim C.