[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371533 ] Andreas Korneliussen commented on DERBY-1097: - Rick, I think you need to recompile everything, since you get java.lang.AbstractMethodError. I think there is

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371535 ] Andreas Korneliussen commented on DERBY-1097: - Actually, I think isClosed() is introduced in JDBC 4, and EmbedStatement is compiled against the rt of jdk 1.3 or

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371394 ] Kristian Waagan commented on DERBY-1097: I tried it in my environment, and it worked by simply adding the line jdbc4/StatementTest.junit to the jdbc40.runall file. If

Re: [jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

Rick Hillegas (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371372 ] Rick Hillegas commented on DERBY-1097: -- I'm afraid I don't know how to wire this test into the jdbc40 suite. I tried wiring

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ 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:

Re: [jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

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: [

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371481 ] David Van Couvering commented on DERBY-1097: OK, I can get into JIRA again. I'll add this to the jdbc4 test suite as a junit test, and commit it along with the

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371364 ] David Van Couvering commented on DERBY-1097: Hi, Kristian. Sorry to bounce this back, but Rick's latest jdbc40 test suite checkin has thrown a spanner in the

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371366 ] Rick Hillegas commented on DERBY-1097: -- I think that my rototill doesn't affect Kristian's patch. He has written a JUnit test which uses conventional machinery to get a

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371372 ] Rick Hillegas commented on DERBY-1097: -- I'm afraid I don't know how to wire this test into the jdbc40 suite. I tried wiring StatementTest.junit at the end of the jdbc40

Re: [jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

Rick Hillegas (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12370883 ] Rick Hillegas commented on DERBY-1097: -- Hi Kristian, 1) I'm afraid I'm missing some context here. It looks like you have some idea of how

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371051 ] Kristian Waagan commented on DERBY-1097: Answering Rick's comments of 17th of March. 1) As is already stated, this test can be run from any suite by simply adding it

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12370910 ] David Van Couvering commented on DERBY-1097: There is a jdbc4 suite. You can add any JUnit test to a suite using the .junit extension (e.g. StatementTest.junit).