Using Vertica with ADF (jar file built with jdk5)
Posted: Tue Mar 18, 2014 7:02 am
Hello --- We are doing a Proof-of-Concept/Demo with Oracle's ADF Fusion Middleware. One of our developers got this stack trace (using vertica 6.1.3-0 jar file):
A little disassembly of the SForwardResultSet shows that the exception is correct.. There IS NO isClosed() method. It has been required by the java.sql.Result interface since Java 1.6, so at first I had a hard time understanding how Vertica even produced such a class without that method. Then I looked at the major/minor version... it's 49.0, which means it was produced with a JDK 1.5 compiler. Then it hit me... that's why the JAR files contain jdk_5 in the filename.
We absolutely CANNOT change Oracle ADF to not call ResultSet.isClosed().
Would it be possible to get Vertica to produce a JAR file against the 1.7 JDBC API quickly?
Several other required methods have been added to the java.sql packages since 1.5.
My only alternative would be to try to disassemble the class files to (uncommented) source, try to add in the new methods, recompile and repackage/patch to create a Frankenstein JDBC driver for our ADF folks to use. SCRATCH THAT.. my disassembler is not even producing compilable code. HELP!
Timothy Jones
tim@timjones.com
timothy.jones@syniverse.com
Code: Select all
java.lang.AbstractMethodError: com.vertica.jdbc.SForwardResultSet.isClosed()Z
at oracle.jbo.server.QueryCollection.setResultSetState(QueryCollection.java:6384)
at oracle.jbo.server.QueryCollection.setResultSet(QueryCollection.java:736)
at oracle.jbo.server.ViewObjectImpl.setResultSetForCollection(ViewObjectImpl.java:7994)
(goes on and on, 400 or so more stack frames)
We absolutely CANNOT change Oracle ADF to not call ResultSet.isClosed().
Would it be possible to get Vertica to produce a JAR file against the 1.7 JDBC API quickly?
Several other required methods have been added to the java.sql packages since 1.5.
My only alternative would be to try to disassemble the class files to (uncommented) source, try to add in the new methods, recompile and repackage/patch to create a Frankenstein JDBC driver for our ADF folks to use. SCRATCH THAT.. my disassembler is not even producing compilable code. HELP!
Timothy Jones
tim@timjones.com
timothy.jones@syniverse.com