[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440684 ]
Tomohito Nakayama commented on DERBY-1610:
------------------------------------------
I think I could find reason for compatibility error ....
Next error was found in serverVM-1.3_serverTrunk_clientVM-1.3_clientTrunk when
compatibility test was executed and failed.
.E.
Time: 2.974
There was 1 error:
1)
testJDBCDriver(org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest)java.lang.NoClassDefFoundError:
java/sql/ParameterMetaData
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:703)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:133)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:320)
at java.net.URLClassLoader.access$400(URLClassLoader.java:93)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:678)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:239)
at java.lang.ClassLoader.loadClass(ClassLoader.java:516)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:460)
at java.lang.ClassLoader.loadClass(ClassLoader.java:448)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newParameterMetaData(ClientJDBCObjectFactoryImpl.java:348)
at
org.apache.derby.client.am.PreparedStatement.getParameterMetaDataX(PreparedStatement.java:1774)
at
org.apache.derby.client.am.PreparedStatement.getParameterMetaData(PreparedStatement.java:1759)
at
org.apache.derby.client.am.PreparedStatement.setInt(PreparedStatement.java:562)
at
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest.setRow(JDBCDriverTest.java:655)
at
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest.stuffTable(JDBCDriverTest.java:377)
at
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest.datatypesTest(JDBCDriverTest.java:281)
at
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.JDBCDriverTest.testJDBCDriver(JDBCDriverTest.java:258)
at
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.main(CompatibilitySuite.java:138)
FAILURES!!!
Tests run: 2, Failures: 0, Errors: 1
Reading javadoc for ParameterMetadata interface, I found we can use this class
after jdk.1.4.
http://java.sun.com/j2se/1.4.2/docs/api/java/sql/ParameterMetaData.html
I think using ParameterMetadata is reason why compatibility suite was failed.
> Resolve difference of type compatibility between Embedded and
> NetworkServer/NetworkDriver
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-1610
> URL: http://issues.apache.org/jira/browse/DERBY-1610
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Network Client
> Reporter: Tomohito Nakayama
> Assigned To: Tomohito Nakayama
> Attachments: DERBY-1610.diff, DERBY-1610_2.diff, DERBY-1610_3.diff,
> DERBY-1610_4.diff, DERBY-1610_5.diff, DERBY-1610_6.patch, DERBY-1610_7.patch,
> DERBY-1610_7_regressionfix.patch, parameterMapping.diff,
> parameterMapping.diff,
> parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient,
> parameterMapping.out.7.diff, parameterMapping.out.diff,
> parameterMapping_3.diff, TestNullChar.java, TestTypeCompatibility.java,
> XCL12.diff
>
>
> There exists difference of type compatibility between Embedded and
> NetworkServer/NetworkClient.
> This issue tries to resolve it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
