Return-Path: X-Original-To: apmail-geronimo-user-archive@www.apache.org Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E64DF73E0 for ; Fri, 2 Sep 2011 08:36:02 +0000 (UTC) Received: (qmail 45594 invoked by uid 500); 2 Sep 2011 08:36:02 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 45055 invoked by uid 500); 2 Sep 2011 08:35:55 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 45047 invoked by uid 99); 2 Sep 2011 08:35:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 08:35:52 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 08:35:46 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QzPDg-0001sW-Qd for user@geronimo.apache.org; Fri, 02 Sep 2011 01:35:24 -0700 Date: Fri, 2 Sep 2011 01:35:24 -0700 (PDT) From: amergey To: user@geronimo.apache.org Message-ID: <1314952524812-3303655.post@n3.nabble.com> Subject: JDBC 4 support in Geronimo 3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Testing a web application executing some JDBC code using a datasource against geronimo 3, I had the following exception "java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z" when calling java.sql.ResultSet.isClose() So it seems geronimo 3 does not support JDBC 4 API, the bug [GERONIMO-6138] (JDBC 4 API is not supported) was closed claiming this bug was fixed in trunk since 3.0-M1 but I have tested with latest available SNAPSHOTS (geronimo-tomcat7-javaee6-web-3.0-20110901.085007-314-bin and geronimo-tomcat7-javaee6-3.0-20110901.110425-314-bin) and the issue is still there Is there something I missed ? meaning is there any way to configure a datasource for supporting JDBC 4 API ? if it is not can I reopen the bug ? Thanks and Regards, Arnaud -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/JDBC-4-support-in-Geronimo-3-tp3303655p3303655.html Sent from the Users mailing list archive at Nabble.com.