Forum Discussion
Hi RPriya
Your trouble may come from the java version update between SoapUI versions.
"The application class loader is no longer an instance of java.net.URLClassLoader (an implementation detail that was never specified in previous releases). Code that assumes that ClassLoader::getSytemClassLoader returns a URLClassLoader object will need to be updated. Note that Java SE and the JDK do not provide an API for applications or libraries to dynamically augment the class path at run-time."
https://www.oracle.com/java/technologies/javase/v9-issues-relnotes.html
It seems that nobody found a real solution since Java 9 version.
You can have a look at the last message of this thread:
https://community.oracle.com/tech/developers/discussion/4011800/base-classloader-no-longer-from-urlclassloader
And try to find a workaround, but I suggest you ask from help to the Smartbear support team.
David.
- RPriya4 years agoNew Contributor
Hi David,
Thanks for your kind reply. I am managing with the work around to keep the jar files in local path of SoapUI installation. So I can avoid loading them using script.
Cheers
Related Content
- 2 years ago
Recent Discussions
- 15 years ago