geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-6138) JDBC 4 API is not supported
Date Tue, 09 Apr 2013 04:16:16 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor resolved GERONIMO-6138.
-----------------------------------

    Resolution: Fixed

I'm resolving this issue as TranQL 1.8 has been released and things in Geronimo are looking
good.

                
> 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
>            Assignee: Jarek Gawor
>             Fix For: 3.0.1
>
>         Attachments: geronimo.patch, tranql.patch
>
>
> 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

Mime
View raw message