How come you can get to JIRA and I can't? Hmph.
Anyway, the reason you are getting this is because the functionality
Statement.isClosed() is not yet implemented (that's the patch I am
trying to commit once I get access to JIRA).
David
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371474 ]
Rick Hillegas commented on DERBY-1097:
--------------------------------------
Now when I add jdbc/StatementTest.junit to the end of jdbc40.runall, I get the
following diffs in the network and embedded runs:
*** Start: StatementTest jdk1.6.0-beta2 jdbc40:jdbc40 2006-03-22 13:30:46 ***
0 add
.E.E.E.E.E
There were 5 errors:
1)
testIsClosedBasic(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
2)
testIsClosedWithTwoStatementsOnSameConnection(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
3)
testIsClosedWhenClosingConnection(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
4)
testIsClosedWhenClosingConnectionInInvalidState(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
5)
testStatementExecuteAfterConnectionClose(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
FAILURES!!!
Tests run: 5, Failures: 0, Errors: 5
Test Failed.
*** End: StatementTest jdk1.6.0-beta2 jdbc40:jdbc40 2006-03-22 13:31:12 ***
I see the following output in StatementTest.tmp:
.E.E.E.E.E
Time: 7.125
There were 5 errors:
1)
testIsClosedBasic(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
at
org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest.setUp(StatementTest.java:63)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
2)
testIsClosedWithTwoStatementsOnSameConnection(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
at
org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest.setUp(StatementTest.java:63)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
3)
testIsClosedWhenClosingConnection(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
at
org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest.setUp(StatementTest.java:63)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
4)
testIsClosedWhenClosingConnectionInInvalidState(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
at
org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest.setUp(StatementTest.java:63)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
5)
testStatementExecuteAfterConnectionClose(org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest)java.lang.AbstractMethodError:
org.apache.derby.impl.jdbc.EmbedStatement.isClosed()Z
at
org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTest.setUp(StatementTest.java:63)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
FAILURES!!!
Tests run: 5, Failures: 0, Errors: 5
I am at subversion rev 387925.
Add tests for Statement.isClosed()
----------------------------------
Key: DERBY-1097
URL: http://issues.apache.org/jira/browse/DERBY-1097
Project: Derby
Type: Sub-task
Components: Test
Versions: 10.2.0.0
Environment: JDBC4 / JDK 1.6
Reporter: Kristian Waagan
Assignee: Kristian Waagan
Attachments: DERBY-1097-2a.diff, DERBY-1097-2a.stat, DERBY-1097-2b.diff,
StatementTest.java, StatementTest.java-v1, StatementTestSetup.java,
StatementTestSetup.java-v1
Add tests for Statement.isClosed() (implemented as part of DERBY-953).
The tests are already written, but because of some "confusion" and diverging
paths regarding how to get connections when running JUnit tests, they are held back.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
