[ 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 jdk1.4. So it is possible to compile Derby without having the isClosed() method in EmbedStatement implemented. So you probably need to download the patch in DERBY-953 to make the test succeed. > 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. -- 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
