[ http://issues.apache.org/jira/browse/DERBY-942?page=comments#action_12413703 ]
Kristian Waagan commented on DERBY-942: --------------------------------------- What you describe can be done by deleting the two subclasses in ConnectionTest, clean up the suite() method, adjust the documentation and add ConnectionTest to the xa suite. I suppose we do not really need the pooled connection test, as the connection implementation class is the same as for xa. Unless someone wants to keep the test as it is (where regular, pooled and xa connections are all tested), I will add a Jira and rewrite the neccessary parts of the test class in a few days. > Add JDBC4 Ease of Development Support > ------------------------------------- > > Key: DERBY-942 > URL: http://issues.apache.org/jira/browse/DERBY-942 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Assignee: Anurag Shekhar > Fix For: 10.2.0.0 > Attachments: TestDbMetaData.diff, TestQueryObject.diff, > derby-942-enable-connectionTest.diff, derby-942-enable-connectionTest.stat, > derby-942.diff, derby-942_2.diff > > As described in the JDBC 4 spec, sections 20.1, 20.2, and 3.1. > The Ease of Development extensions provide a way to create tabular DataSets > from queries and tuple signatures. The jdk ships with a factory for creating > these DataSets, which is a class which implements the QueryObjectGenerator > interface. A database can write its own custom QueryObjectGenerator, or just > ship with the default, jdk-shipped version. For this task, we will simply > wire the default jdk-shipped factory into the appropriate methods: > Connection.createQueryObject() and DataSource.createQueryObject(). -- 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
