[ http://issues.apache.org/jira/browse/DERBY-1063?page=comments#action_12368060 ]
Daniel John Debrunner commented on DERBY-1063: ---------------------------------------------- I'm confused by the description of this issue, auto-loading a driver to me means that the application no longer needs to have this line in their code: Class.forName(driverName); Adding a Class-path entry does not auto-load a driver, or load the jar file, it just adds the jar file to the class path. JDBC 4.0 is adding an auto-load of the JDBC driver which is entered as DERBY-930 > Autoloading of JDBC drivers via derbytools.jar manifest Class-Path attribute > ---------------------------------------------------------------------------- > > Key: DERBY-1063 > URL: http://issues.apache.org/jira/browse/DERBY-1063 > Project: Derby > Type: Improvement > Components: Tools > Versions: 10.2.0.0 > Reporter: Andrew McIntyre > Assignee: Andrew McIntyre > Attachments: derby1063.diff > > Support autoloading of JDBC drivers via derbytools.jar manifest Class-Path > attribute. Originally added as part of DERBY-1019, this was removed as a > result of DERBY-1045. Attaching a patch to reinstitute the Class-Path > attribute for derbytools.jar, along with an improvement to sysinfo to report > the location of the jars from which the info properties files are loaded. > Note that this does not attempt to mitigate the current problems running > sysinfo under a security manager, but to improve the reporting of the > locations of the loaded files if they are not loaded from the classpath. -- 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
