commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32964] - [dbcp] PoolingDriver.getConnectionPool() should use contextClassLoader
Date Fri, 07 Jan 2005 19:18:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32964>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32964





------- Additional Comments From carl@calmetrics.com  2005-01-07 20:18 -------
The same goes for BasicDataSource.createDataSource()
This function uses Class.forName(driverClassName) to try and
load the JDBC driver. Of course, this uses the classloader
that loaded BasicDataSource. So, if BasicDataSource is part of your
regular application (on classpath, loaded by the AppClassLoader),
and you dynamically load a new JAR containing the JDBC driver, you're out of
luck. Using the contextClassLoader would solve this problem. Using the 3-arg
variant of Class.forName() would work.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message