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 Fri, 28 Apr 2006 13:30:40 GMT
     [ http://issues.apache.org/jira/browse/DERBY-941?page=all ]

V.Narayanan updated DERBY-941:

    Attachment: statementeventlisteners_client_v3.diff

Hi Knut, 
"why do I keep doing this to myself :-( ". Again a result of my patch for 1254. 1254 changes
createNetConnection to use ClientJDBCObjectFactory to return an appropriate instance of NetConnection(or40).
 I had to pass the reference to ClientPooledConnection to this method. I have done it in the
attached patch. I have also attached the diff between the previous and the current patch.

Please accept my humble apologies for the inconvinience caused.


> 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: ListenerTest.java, diff_between_ver2_ver3.txt, statementeventlisteners_client.diff,
statementeventlisteners_client.html, statementeventlisteners_client.stat, statementeventlisteners_client_v1.diff,
statementeventlisteners_client_v1.stat, statementeventlisteners_client_v2.diff, statementeventlisteners_client_v2.stat,
statementeventlisteners_client_v3.diff, statementeventlisteners_client_v3.stat, statementeventlisteners_embedded.diff,
statementeventlisteners_embedded.stat, statementeventlisteners_embedded_v2.diff, statementeventlisteners_embedded_v2.stat,
statementeventlisteners_embedded_v3.diff, statementeventlisteners_embedded_v3.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