Apologies if this is the wrong forum but I couldn't find a suitable category.
I'm writing an EJB that operates on a database using SQL via the standard JDBC libraries. Sadly, some of these methods whilst are declared to throw SQLException yet at the same time, throw some unchecked exceptions. What is the best design methodology to follow, since my EJB must check for these to save the service from going down? I am trying to avoid having a "catch-all" scenario, where I shove catch Exception and catch Throwable around the potential problem. [Message sent by forum member 'rioch' (rioch)] http://forums.java.net/jive/thread.jspa?messageID=249518 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
