[DBCP-310] SQLNestedException & use of initCause() with SQLException

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.3, 1.4
• Assignee: Unassigned
• Reporter: Niall Pemberton
• Created: 28/Nov/09 16:28
• Updated: 15/Feb/10 01:49
• Resolved: 29/Nov/09 00:13

Description

SQLNestedException in its current state is a hangover from supporting JDK 1.3 when there was no "initCause()" method. This implementation can now be greatly simplified with DBCP now having a minimum of JDK 1.4

Also SQLNestedException is deprecated and the following code has been used in a number of places

     throw (SQLException )new SQLException(message).initCause(e)

DBCP is inconsistent though - sometimes using the above and sometimes using SQLNestedException. IMO SQLNestedException should be un-deprecated and used consistently everywhere - its now a simple implementation and I think the code is cleaner using it rather than the above.

Issue Links

• is related to: DBCP-143 [dbcp] SQLNestedException thrown by server causes client ClassNotFoundException.