Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 18 Feb 2014 18:50:19 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12690886.1390512329771.58817.1392749419651@arcas>
In-Reply-To: <JIRA.12690886.1390512329771@arcas>
References: <JIRA.12690886.1390512329771@arcas>
Subject: [jira] [Commented] (DERBY-6459) Remove Class.forName calls that
 load JDBC driver from Derby samples/demos
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Committed patch DERBY-6459-2.diff to code trunk at revision 1569470.

> 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)