[ http://issues.apache.org/jira/browse/DERBY-940?page=comments#action_12372723 ]
Rick Hillegas commented on DERBY-940: ------------------------------------- Hi Narayanan, Thanks for all the good work. I think that, going forward, we should stop writing the old-style tests and concentrate on writing JUnit tests. With a little effort, you should be able to recast TestDataSourceMethods as a junit test extending BaseJDBCTestCase. If you do that, then you can eliminate the main() method and the "if(usingEmbeddedClient())" logic. Thanks to some recent work, you can now get the DataSource in a client-agnostic way from BaseJDBCTestCase.getDataSource(). To prevent the test from running under the Network client, you should add the test name (and a comment) to java/testing/org/apache/derbyTesting/functionTests/suites/DerbyNetClient.exclude. I think that Kristian has a good solution to the problem of excluding individual test cases from client-specific runs. In any event, the exclusion is a temporary piece of scaffolding which you will be removing soon enough. > Add JDBC 4 Wrapper support > -------------------------- > > Key: DERBY-940 > URL: http://issues.apache.org/jira/browse/DERBY-940 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Assignee: V.Narayanan > Fix For: 10.2.0.0 > Attachments: DERBY940_embedded.html, wrapper_ver1_embedded.diff, > wrapper_ver1_embedded.stat, wrapper_ver2_embedded.diff, > wrapper_ver2_embedded.stat, wrapper_ver3_embedded.diff, > wrapper_ver3_embedded.stat > > As described in the JDBC 4 spec, sections 21 and 3.1. -- 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
