Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 44587 invoked from network); 27 Apr 2007 00:03:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Apr 2007 00:03:39 -0000 Received: (qmail 2613 invoked by uid 500); 27 Apr 2007 00:03:44 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 2478 invoked by uid 500); 27 Apr 2007 00:03:43 -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 2196 invoked by uid 99); 27 Apr 2007 00:03:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2007 17:03:43 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2007 17:03:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B0C1A71407D for ; Thu, 26 Apr 2007 17:03:15 -0700 (PDT) Message-ID: <12002209.1177632195721.JavaMail.jira@brutus> Date: Thu, 26 Apr 2007 17:03:15 -0700 (PDT) From: "Daniel John Debrunner (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2582) EmbeddedConnectionPoolDataSource does not implement java.sql.Wrapper but reports JDBC 4 compliance when run with JDK 6 In-Reply-To: <26763197.1177355775280.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492159 ] Daniel John Debrunner commented on DERBY-2582: ---------------------------------------------- Simpler check would be ds instanceof java.sql.Wrapper > EmbeddedConnectionPoolDataSource does not implement java.sql.Wrapper but reports JDBC 4 compliance when run with JDK 6 > ----------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2582 > URL: https://issues.apache.org/jira/browse/DERBY-2582 > Project: Derby > Issue Type: Sub-task > Components: JDBC > Affects Versions: 10.2.2.1 > Environment: JDK 6 > Reporter: Stan Bradbury > > Software that checks the value returned by the dataseMetadata method getJDBCMajorVersion for JDBC compliance level and, based on the value, takes different paths in the code will fail unexpectedly accessing java.sql.Wrapper when loading EmbeddedConnectionPoolDataSource in a JDK 6 environment. EmbeddedConnectionPoolDataSource reports a compliance level of 4 when loaded in a JDK 6 environment. It returns JDBC 4 objects but the Datasource itself does NOT satify the JDBC 4.0 interface Wrapper and so, not being fully compliant, should not report JDBC 4 compliance. > JSR 221 does not detail the behavior of the dataseMetadata method getJDBCMajorVersion but the description in Section 6.3, JDBC 4.0 API Compliance, states: "A driver that is compliant with the JDBC 4.0 specification must .. Fully implement .. java.sql.Wrapper". As Dan stated in his comment on DERBY-2488, (http://issues.apache.org/jira/browse/DERBY-2488#action_12485033) EmbeddedConnectionPoolDataSource does not implement Wrapper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.