db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6459) Remove Class.forName calls that load JDBC driver from Derby samples/demos
Date Tue, 18 Feb 2014 18:48:20 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904393#comment-13904393
] 

Kim Haase commented on DERBY-6459:
----------------------------------

Thanks, Rick, for recommending in a DERBY-6482 comment that I check in what I have now. I'm
leaving the issue open for additional VTI-related changes.

> Remove Class.forName calls that load JDBC driver from Derby samples/demos
> -------------------------------------------------------------------------
>
>                 Key: DERBY-6459
>                 URL: https://issues.apache.org/jira/browse/DERBY-6459
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Demos/Scripts
>    Affects Versions: 10.11.0.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-6459-2.diff, DERBY-6459.diff, DERBY-6459.stat
>
>
> Several of the Derby samples and demos call Class.forName to load the JDBC driver, although
this is not necessary at Java SE 6 and later. Since at 10.11 we won't support versions of
the platform earlier than JDK 6, these calls should be removed from the samples (and any mention
of them removed from the accompanying documentation).
> There are calls to Class.forName that load other objects besides the driver; I assume
these are still needed, but if not, they could be replaced with something more current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message