commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <>
Subject [dbcp] fix for DBCP-333 - DriverManager no longer used to load drivers
Date Mon, 25 Apr 2011 23:33:21 GMT
Prior to the fix for DBCP-333, DriverManager was always used to load
drivers.  As documented in the patch and updated javadoc,
DriverManager is now used only when loading via configured
driverClassLoader or the context classloader fails.  Might this
change cause problems for implementations that somehow rely on the
fact that DBCP has up to now used DriverManager to load drivers? 
What brought it to mind for me was the test case submitted in the
patch for DBCP-342, which did rely on this (undocumented) behavior.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message