You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2019/01/29 14:31:00 UTC
[jira] [Commented] (DERBY-7032) Developer's Guide recommends use of
a deprecated method
[ https://issues.apache.org/jira/browse/DERBY-7032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755057#comment-16755057 ]
Kim Haase commented on DERBY-7032:
----------------------------------
This pattern occurs in a couple of places in the Reference Manual as well as the Dev Guide. I thought there were more.
> Developer's Guide recommends use of a deprecated method
> -------------------------------------------------------
>
> Key: DERBY-7032
> URL: https://issues.apache.org/jira/browse/DERBY-7032
> Project: Derby
> Issue Type: Bug
> Components: Documentation, JDBC
> Affects Versions: 10.15.1.1, 10.16.0.0
> Reporter: Rick Hillegas
> Priority: Major
>
> The "Shutting down the system" topic in the Developer's Guide (and probably other places in the user documentation) recommends the following pattern for re-loading the engine driver after it was unloaded by a graceful system shutdown:
> {noformat}
> Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance();
> {noformat}
> However, if you use Java 9 or later to compile an application which follows that pattern, then you will get a deprecation warning. That is because Java 9 deprecated Class.newInstance(). Some future rev of the JDK may remove the method altogether.
> This issue was discovered while investigating DERBY-7031.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)