db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-941) Add JDBC4 support for Statement Events
Date Mon, 17 Apr 2006 14:21:18 GMT
     [ http://issues.apache.org/jira/browse/DERBY-941?page=all ]

V.Narayanan updated DERBY-941:

    Attachment: statementeventlisteners_embedded_v2.diff

Primary change has been to the class org.apache.derbyTesting.functionTests.util.TestUtil

The getConnectionPoolDataSource() method had to be changed to return either EmbedConnectionPoolDataSource
or EmbedConnectionPoolDataSource40 depending
on the jdk version under use.

I have moved the code for determining whether we need to use a 40 class to the method checkForJDBC40Implementation
this method returns a String representing the correct name of the class to be used.

I have changed the constant UNABLE_TO_UNWRAP in SQLConstants.java to hold the value "XJ128"
instead of the existing "XJ120" to allow the jdbc4 tests to run correctly. This is causing
failures in the jdbc4 tests currently. Once
this issue is fixed it can be removed from this patch also.


> Add JDBC4 support for Statement Events
> --------------------------------------
>          Key: DERBY-941
>          URL: http://issues.apache.org/jira/browse/DERBY-941
>      Project: Derby
>         Type: New Feature

>   Components: JDBC
>     Versions:
>     Reporter: Rick Hillegas
>     Assignee: V.Narayanan
>  Attachments: statementeventlisteners_embedded.diff, statementeventlisteners_embedded.stat,
statementeventlisteners_embedded_v2.diff, statementeventlisteners_embedded_v2.stat, statementeventlisteners_embedded_ver1.html
> As described in the JDBC 4 spec, sections 11.2, 11.7,  and 3.1.
> These are the methods which let app servers listen for connection and statement closure
and invalidation events.
> Section 11.2 of the JDBC 4 spec explains connection events: Connection pool managers
which implement the ConnectionEventListener interface can register themselves to listen for
 "connectionClosed" and fatal "connectionErrorOccurred" events. App servers can use these
events to help them manage the recycling of connections back to the connection pool.
> Section 11.7 of the JDBC 4 spec explains statement events: Statement pools which implement
StatementEventListener can register themselves to listen for "statementClosed" and "statementErrorOccurred"
events. Again, this helps statement pools manage the recycling of statements back to the pool.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message