Project: Birt
Bug 224255 Null point exception for empty JDBC driver folder if 'OdaJDBCDriverClassPath' app context is specified
Reported: 2008-03-26 19:43:12 | Status: resolved fixed

Build ID: I20070621-1340 Steps To Reproduce: If the OdaJDBCDriverClassPath is specified as the appContext of the conenction with the empty JDBC driver folder, the null pointer excpetion will occur, this is due to the null value of Enumeration files in the refreshURLs() method of JDBCDriverManager. The detail call stack has been attached. More information: JDBCDriverManager$DriverClassLoader.refreshURLs() line: 923 JDBCDriverManager$DriverClassLoader.<init>(String) line: 855 JDBCDriverManager.loadExtraDriver(String, boolean, String) line: 815 JDBCDriverManager.findDriver(String, String) line: 668 JDBCDriverManager.loadAndRegisterDriver(String, String) line: 783 JDBCDriverManager.doConnect(String, String, String, Properties, String) line: 195 JDBCDriverManager.getConnection(String, String, String, Properties, String) line: 161 Connection.connectByUrl(String, Properties) line: 158 Connection.open(Properties) line: 115 OdaConnection.open(Properties) line: 235 ConnectionManager.openConnection(String, Properties, Map) line: 111 DataSource.newConnection() line: 126 DataSource.getAvailableConnection() line: 181 DataSource.open() line: 120 DataExecutionAgent.open() line: 188 DataExecutionAgent.run() line: 299 Thread.run() line: 595

Files changed in fix:
data/org.eclipse.birt.report.data.oda.jdbc/src/org/eclipse/birt/report/data/oda/jdbc/JDBCDriverManager.java