[
https://issues.apache.org/jira/browse/DERBY-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229446#comment-13229446
]
Rick Hillegas commented on DERBY-5519:
--------------------------------------
Hi Kathey,
The current 10.8 behavior looks correct to me. There was a little more work
needed in order to make Derby fully support JDBC 4.1. That work was done on the
trunk under DERBY-5488. I would not change the 10.8 J2SE_17 case unless the
work on DERBY-5488 is backported to 10.8 also. Thanks.
> Update code in JVMInfo#derbyVMLevel to give correct results for Java 7 and
> provisionally for 8.
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-5519
> URL: https://issues.apache.org/jira/browse/DERBY-5519
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Labels: newbie
> Fix For: 10.9.0.0
>
> Attachments: derby-5519.diff
>
>
> The method derbyVMLevel gives correct result only up to and including Java 6,
> cf. this snippet:
> public static String derbyVMLevel()
> {
> switch (JDK_ID)
> {
> case J2SE_14: return J2ME ? "J2ME - JDBC for CDC/FP 1.1" : "J2SE 1.4 -
> JDBC 3.0";
> case J2SE_142: return "J2SE 1.4.2 - JDBC 3.0";
> case J2SE_15: return "J2SE 5.0 - JDBC 3.0";
> case J2SE_16: return "Java SE 6 - JDBC 4.0";
> default: return "?-?";
> }
> }
> This is exposed through our MBean implementation in
> org.apache.derby.jdbc.JDBC#getDriverLevel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
