db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oyvind Bakksjo (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-503) Documentation should recommend using .newInstance() to instantiate JDBC driver
Date Fri, 12 Aug 2005 09:02:54 GMT
Documentation should recommend using .newInstance() to instantiate JDBC driver
------------------------------------------------------------------------------

         Key: DERBY-503
         URL: http://issues.apache.org/jira/browse/DERBY-503
     Project: Derby
        Type: Improvement
  Components: Documentation  
    Versions: 10.1.1.0    
    Reporter: Oyvind Bakksjo
    Priority: Minor


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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message