[DERBY-1638] JUnit TestConfiguration class uses engine code to determine JDBC level.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 10.2.1.6
• Component/s: Test
• Assignee: Daniel John Debrunner
• Reporter: Daniel John Debrunner
• Created: 03/Aug/06 05:24
• Updated: 06/Aug/06 16:55
• Resolved: 06/Aug/06 16:55

Description

TestConfiguration uses the org.apache.derby.iapi.services.info.JVMInfo to determine if JDBC 4 is supported. Ideally test code should not be calling engine private api code.

Suggest two changes:

1) Determine JDBC level support from ability to load classes:
E.g. JDBC2 - java.sql.Driver
JDBC3 - java.sql.Driver AND java.sql.ParameterMetaData
JDBC4 - java.sql.Driver AND java.sql.SQLXML
JSR169 - java.sql.ParameterMetaData AND NOT java.sql.Driver

2) Move the supportsJDBC4() method from TestConfiguraiton to JDBC, since if the VM supports JDBC4 or not is
not an attribute of a test configuration (and add other supportsJDBCX methods).