[
https://issues.apache.org/jira/browse/DERBY-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-503.
-----------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Derby Info: (was: [Patch Available])
Committed patch DERBY-503-2.diff to documentation trunk at revision 689598.
> Documentation should recommend using .newInstance() to instantiate JDBC driver
> ------------------------------------------------------------------------------
>
> Key: DERBY-503
> URL: https://issues.apache.org/jira/browse/DERBY-503
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.1.1.0
> Reporter: Oyvind Bakksjo
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: DERBY-503-2.diff, DERBY-503-2.zip, DERBY-503.diff,
> DERBY-503.stat, DERBY-503.zip
>
>
> Using Class.forName("<driver name>").newInstance() is the recommended way to
> load and instantiate the JDBC driver, but the documentation does not contain
> the .newInstance() part.
> Pointers:
> http://db.apache.org/derby/docs/10.1/devguide/cdevdvlp40653.html
> http://db.apache.org/derby/docs/10.1/ref/rrefjdbc32052.html
> The EmbeddedDriver javadoc mentions it:
> "The JDBC specification recommends the Class.ForName method without the
> .newInstance() method call, but adding the newInstance() guarantees that
> Derby will be booted on any Java Virtual Machine."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
