Forum Discussion
SmartBear_Suppo
Alumni
15 years agoHello,
In soapUI 3.6.1 we made some changes to how certain classes are loaded, which unfortunately has this side effect... To fix the problem, you have two options. Either you add the following line to the beginning of any script where you need the driver:
Or, if you have a lot of scripts and don't want to modify them all, you can alternatively move the driver jar file from the ext folder to the lib folder instead, and it should work. This won't work with our other load testing tool, loadUI, though. Because of this, I would recommend using the first approach. Good luck!
Regards,
Dain
eviware.com
In soapUI 3.6.1 we made some changes to how certain classes are loaded, which unfortunately has this side effect... To fix the problem, you have two options. Either you add the following line to the beginning of any script where you need the driver:
com.eviware.soapui.support.GroovyUtils.registerJdbcDriver("oracle.jdbc.driver.OracleDriver")
Or, if you have a lot of scripts and don't want to modify them all, you can alternatively move the driver jar file from the ext folder to the lib folder instead, and it should work. This won't work with our other load testing tool, loadUI, though. Because of this, I would recommend using the first approach. Good luck!
Regards,
Dain
eviware.com