On Jan 7, 2007, at 6:41 PM, Karan Malhi wrote:
also at some places I see e.printStackTrace() in the catch block.
Is there
any specific reason why we are printing the stack trace at some
places,
whereas throwing an OpenEJBException at some other places? What is the
general exception handling strategy?
Probably anything that calls printStackTrace could stand some better
exception handling.
Ideally every exception would be very detailed, localized, nested and
the e.getMessage() text contain at least some hint of the nested
exception. But obviously reality often falls short of that.
-David
