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] [Closed] (DERBY-6459) Remove Class.forName calls that load JDBC driver from Derby samples/demos
Date Wed, 17 Sep 2014 13:58:38 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase closed DERBY-6459.
----------------------------

Closing, though there's an unresolved question that came up post-resolution. Feel free to
reopen if need be.

> 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.1.1
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>             Fix For: 10.11.1.1
>
>         Attachments: DERBY-6459-2.diff, DERBY-6459-3.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.3.4#6332)

Mime
View raw message