Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Mon, 4 Mar 2013 07:45:15 +0000 (UTC)
From: "Bart van Leeuwen (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: <JIRA.12521070.1314891290803.373960.1362383115193@arcas>
In-Reply-To: <JIRA.12521070.1314891290803@arcas>
References: <JIRA.12521070.1314891290803@arcas>
Subject: [jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592047#comment-13592047 ] 

Bart van Leeuwen commented on GERONIMO-6138:
--------------------------------------------

*bump*

I'm running into some JDBC4 limitations with IBM DB2 v10.1 and WASCE 3.0.2. I need JDBC4 support in WASCE.
                
> JDBC 4 API is not supported 
> ----------------------------
>
>                 Key: GERONIMO-6138
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6138
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 3.0-M1, 3.0.0
>            Reporter: Arnaud MERGEY
>             Fix For: 3.0.1
>
>
> I try to deploy an application that uses some JDBC 4 API like java.sql.ResultSet.isClosed()
> This calls fails with following error
> java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z
> According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo 3, and it seems not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira