Assign relevant errors to late-breaking new JDBC4 SQLException subclass:
SQLRecoverableException
------------------------------------------------------------------------------------------------
Key: DERBY-1239
URL: http://issues.apache.org/jira/browse/DERBY-1239
Project: Derby
Type: New Feature
Components: JDBC
Versions: 10.2.0.0
Reporter: Rick Hillegas
Fix For: 10.2.0.0
An upcoming jdk16 release will expose another new subclass of SQLException:
SQLRecoverableException. Here is the verbiage from the draft SQLException
chapter of the next rev of the JDBC4 spec:
---------------------------------------------------------------------------------------
7.5.3 SQLRecoverableException
A SQLRecoverableException would be thrown in situations where the failed
operation might succeed if the application performs some recovery steps and
retries
the entire transaction or in the case of a distributed transaction, the
transaction
branch. At a minimum, recovery includes closing the current connection and
getting
a new one. After a SQLRecoverableException the application must assume that
the connection is no longer valid.
-------------------------------------------------------------------
And here is the upcoming new javadoc header for this class:
java.sql
Class SQLRecoverableException
java.lang.Object
extended by java.lang.Throwable
extended by java.lang.Exception
extended by java.sql.SQLException
extended by java.sql.SQLRecoverableException
All Implemented Interfaces:
java.io.Serializable, java.lang.Iterable<java.lang.Throwable>
public class SQLRecoverableException
extends SQLException
The subclass of SQLException thrown in situations where a previously failed
operation might be able to succeed if the application performs some recovery
steps and retries the entire transaction or in the case of a distributed
transaction, the transaction branch. At a minimum, the recovery operation must
include closing the current connection and getting a new connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
