[jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624057#comment-13624057 ] Jarek Gawor commented on GERONIMO-6138: --- In revision 1465128 I updated the 3.0 branch to use tranql 1.8 rc. Please try it out. > 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
[VOTE RESULT] (take 2) Release yoko-1.4
Hi all, Here are the vote results: +1: Kevan, Shawn, David, Jarek +0: none -1: none The vote passes. I'll get the artifacts published. Thank you all, Jarek
[jira] [Assigned] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-6138: - Assignee: Jarek Gawor > 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
Re: [tranql-dev] tranql connector release candidate for jdbc 4 support
On Apr 5, 2013, at 3:58 PM, David Jencks wrote: > I've put together a release candidate for the tranql connector projects > staged at > > https://nexus.codehaus.org/content/repositories/orgtranql-016/ > > The main purpose is to support jdbc 4. I also simplified the prepared > statement cache code by moving it to a new abstract MCF class and making the > individual MCFs that support prepared statement caching themselves inherit > from the new abstract class. I also provided a generic wrapper that does PS > caching. Geronimo might want to use this in the @Datasource support, I'm not > sure. > > Please take a look. If there are no problems reported I plan to release > these no sooner than monday. Nice. Thanks David! I know there have been some users quite eager for JDBC4 support. Hoping they'd be willing to give this a try -- would be a great way to validate. --kevan
Re: [VOTE] (take 2) Release yoko-1.4
+1 I can build from the source zip and the legal files look ok to me. thanks! david jencks On Apr 2, 2013, at 8:07 AM, Jarek Gawor wrote: > Hi all, > > I would like to call a vote on yoko-1.4. It is a minor release that > contains TCK related fixes (GERONIMOTCK-133, GERONIMOTCK-142) and > Genesis update to build with Java 7. > > Source archives: > https://repository.apache.org/content/repositories/orgapachegeronimo-052/org/apache/yoko/yoko/1.4/ > > Source tag: > https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.4/ > > Staging repository: > https://repository.apache.org/content/repositories/orgapachegeronimo-052/ > > Vote will be open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1. > > Jarek
tranql connector release candidate for jdbc 4 support
I've put together a release candidate for the tranql connector projects staged at https://nexus.codehaus.org/content/repositories/orgtranql-016/ The main purpose is to support jdbc 4. I also simplified the prepared statement cache code by moving it to a new abstract MCF class and making the individual MCFs that support prepared statement caching themselves inherit from the new abstract class. I also provided a generic wrapper that does PS caching. Geronimo might want to use this in the @Datasource support, I'm not sure. Please take a look. If there are no problems reported I plan to release these no sooner than monday. thanks david jencks
[jira] [Commented] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623924#comment-13623924 ] Bart van Leeuwen commented on GERONIMO-6138: Also create a entry at the WASCE forum: https://www.ibm.com/developerworks/forums/thread.jspa?threadID=484662 > 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 > > 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
