DBCP-143 talks about problem with propagation of SQLNestedException
to clients and the comment suggests a conversion to normal Java
nested exception when we switch to Java 1.4. Since we made the leap,
I did a bit of refactoring to remove this exception class. Basically
I replace:
new SQLNestedException(msg, e);
with:
(SQLException) new SQLException(msg).initCause(e);
I attached this at a patch to 143 as I'm not 100% sure we want to go
this direction.
So, should we drop SQLNestedException?
-dain
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
