Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 29455 invoked from network); 28 Apr 2006 09:26:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Apr 2006 09:26:10 -0000 Received: (qmail 82722 invoked by uid 500); 28 Apr 2006 09:26:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 82693 invoked by uid 500); 28 Apr 2006 09:26:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 82681 invoked by uid 99); 28 Apr 2006 09:26:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 02:26:03 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2006 02:26:03 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B9E3E7142E5 for ; Fri, 28 Apr 2006 09:25:38 +0000 (GMT) Message-ID: <16795615.1146216338759.JavaMail.jira@brutus> Date: Fri, 28 Apr 2006 09:25:38 +0000 (GMT+00:00) From: "V.Narayanan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-941) Add JDBC4 support for Statement Events In-Reply-To: <847461104.1139600944980.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-941?page=comments#action_12376904 ] V.Narayanan commented on DERBY-941: ----------------------------------- sorry for having made u go through the trouble of applying the broken patch. Missed the conflict when I submitted the patches. thanx Narayanan > 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: 10.0.2.0 > Reporter: Rick Hillegas > Assignee: V.Narayanan > Attachments: ListenerTest.java, 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_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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira