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] Commented: (DERBY-941) Add JDBC4 support for Statement Events
Date Mon, 10 Apr 2006 13:45:00 GMT
    [ http://issues.apache.org/jira/browse/DERBY-941?page=comments#action_12373850 ] 

V.Narayanan commented on DERBY-941:

Hi Rick,
Thank you for going through the patch. The class EmbeddedConnectionPoolDataSource40 is being
added as part of derby-1137. I wanted to use the method getPooledConnection() method in EmbedConnectionPoolDataSource40
which will override the existing method in EmbedConnectionPoolDataSource to return a PooledConnection40
object. Since the refractoring of these classes were going on I added a implementation to
my patch to basically demonstrate how the patch will look like once 1137 is through. 

please note that this patch has been added to get comments on my solution and to ensure that
I am progressing in the right direction as far my solution is concerned. This patch is not
ready for commit as yet


> 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,
> 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