[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-tabpanelfocusedCommentId=13624399#comment-13624399 ] Bart van Leeuwen commented on GERONIMO-6138: antiguru provided me a new build, and my testcase works as expected now! now only a new wasce build ;) 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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13608100#comment-13608100
]
Moritz Hoffmann commented on GERONIMO-6138:
---
I was able to build a custom Geronimo with JDBC 4 support for DB2. Here are the
instructions on what needs to be done.
- Checkout tranql and build it. It is available in SVN on
https://svn.codehaus.org/tranql/ra/trunk/
- This will fail as the DB2 driver is not available. Install the db2jcc4 driver
into the local maven repo using
mvn install:install-file -Dfile=${path to db2jcc4.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc4 \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc \
-Dversion=10.1 \
-Dpackaging=jar
mvn install:install-file -Dfile=${path to db2jcc_license_cu.jar} \
-DgroupId=com.ibm.db2 \
-DartifactId=db2jcc_license_cu \
-Dversion=10.1 \
-Dpackaging=jar
- Change the tranql version to 1.8. I used the versions:set maven plug-in, set
the version to 1.8, like this:
mvn versions:set -DnewVersion=1.8
This needs to be done for tranql-connector-[db2,parent,generic].
- Tell the DB2 connector to use db2jcc4:
--- tranql-connector-db2/tranql-connector-db2-common/pom.xml(revision 862)
+++ tranql-connector-db2/tranql-connector-db2-common/pom.xml(working copy)
@@ -34,7 +34,7 @@
dependencies
dependency
groupIdcom.ibm.db2/groupId
-artifactIddb2jcc/artifactId
+artifactIddb2jcc4/artifactId
scopeprovided/scope
/dependency
And:
--- tranql-connector-db2/pom.xml(revision 862)
+++ tranql-connector-db2/pom.xml(working copy)
@@ -44,20 +44,20 @@
/scm
properties
-db2.version9.5/db2.version
+db2.version10.1/db2.version
/properties
dependencyManagement
dependencies
dependency
groupIdcom.ibm.db2/groupId
-artifactIddb2jcc/artifactId
+artifactIddb2jcc4/artifactId
version${db2.version}/version
/dependency
- Try to build the generic and db2 parts and install them in the local
repository (mvn install). If a compile error occurs, then apply the following
patch:
---
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(revision 862)
+++
tranql-connector-db2/tranql-connector-db2-common/src/main/java/org/tranql/connector/db2/XAMCF.java
(working copy)
@@ -54,7 +54,7 @@
public ManagedConnection createManagedConnection(Subject subject,
ConnectionRequestInfo connectionRequestInfo) throws ResourceException {
CredentialExtractor credentialExtractor = new
CredentialExtractor(subject, connectionRequestInfo, this);
-XAConnection sqlConnection = getPhysicalConnection(subject,
credentialExtractor);
+XAConnection sqlConnection =
getPhysicalConnection(credentialExtractor);
try {
ManagedXAConnection mxac = null;
if (preparedStatementCacheSize 0) {
Try to build it again.
- Tell Geronimo to use our custom tranql 1.8 by changing some version numbers:
--- plugins/connector-1_6/pom.xml (revision 1452838)
+++ plugins/connector-1_6/pom.xml (working copy)
@@ -186,7 +186,7 @@
dependency
groupIdorg.tranql/groupId
artifactIdtranql-connector-db2-xa/artifactId
-version1.7/version
+version1.8/version
typerar/type
exclusions
exclusion
--- pom.xml (revision 1452838)
+++ pom.xml (working copy)
@@ -81,8 +81,8 @@
xbeanBundleUtilsVersion3.12/xbeanBundleUtilsVersion
jettyjetty8/jetty
txmanagerVersion3.1.1/txmanagerVersion
-tranqlVersion1.7/tranqlVersion
-tranqlDerbyVersion1.7/tranqlDerbyVersion
+tranqlVersion1.8/tranqlVersion
+tranqlDerbyVersion1.8/tranqlDerbyVersion
jaxbImplVersion2.2.3-1_1/jaxbImplVersion
monitoringConsoleVersion${project.version}/monitoringConsoleVersion
- Patch Geronimo to fix one compile error:
---
plugins/connector-1_6/geronimo-connector-1_6/src/main/java/org/apache/geronimo/datasource/DataSourceService.java
(revision 1452838)
+++
[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-tabpanelfocusedCommentId=13592285#comment-13592285 ] Kevan Miller commented on GERONIMO-6138: For WAS CE support, you'll want to check with IBM. However, this problem has been around for a while in Geronimo. We really should get this fixed. Any volunteers? 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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13462614#comment-13462614 ] Arnaud MERGEY commented on GERONIMO-6138: - Any news on this, Geronimo release claim to Support SUN's Java Enterprise Edition 6.0 Full Profile specification But is still not supporting JDBC4, according to this http://www.oracle.com/technetwork/java/javaee/tech/index-jsp-142185.html, I believe it should 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 Reporter: Arnaud MERGEY Fix For: 3.0 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
[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-tabpanelfocusedCommentId=13095799#comment-13095799 ] Arnaud MERGEY commented on GERONIMO-6138: - I have tried geronimo-tomcat7-javaee6-web-3.0-20110901.085007-314-bin and the issue is still there java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z by calling java.sql.ResultSet.isClosed() 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 Reporter: Arnaud MERGEY Fix For: 3.0 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-tabpanelfocusedCommentId=13095888#comment-13095888 ] Rex Wang commented on GERONIMO-6138: ResultSet adds some new APIs since 1.6, but tranql-connector is built from java 1.5. So some APIs are not implemented... Seems TCK did not cover these changes.. I think we need reopen this jira. -Rex 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 Reporter: Arnaud MERGEY Fix For: 3.0 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
