[ http://issues.apache.org/jira/browse/DERBY-1638?page=all ]
Daniel John Debrunner updated DERBY-1638:
-----------------------------------------
Derby Info: (was: [Patch Available])
Made similar changes to patch. Change from patch is to name the methods
vmSupportsJDBC4 etc. to clearly define it's the level of support provided by
the virtual machine (and not the client for example).
Committed revision 429154.
> JUnit TestConfiguration class uses engine code to determine JDBC level.
> -----------------------------------------------------------------------
>
> Key: DERBY-1638
> URL: http://issues.apache.org/jira/browse/DERBY-1638
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Attachments: derby1638_diff.txt
>
>
> 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).
--
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
