is a great tool for testing web services and works especially well with its automation features. I've been using this tool since as long as I can remember working in the IT industry, only recently moving some of the work over to newer tools like Postman
. So even to this day SoapUI remains my primary testing tool. Unfortunately some time during the 5.2 release of SoapUI a number of plugins were installed that were meant for its Pro features, and now some of these plugins are incompatible with later versions of SoapUI and cause a number of exceptions to be logged while using the Test Runner.
The exception that is thrown is a ClassNotFoundException
thrown when SoapUI is trying to load some of the plugins.
Even though this exception looks menacing, the Test Runner
is not adversely impacted. The tests run...
...and complete without issues.
Yet the logs are filled with these pesky exceptions. So what can be done about them? Simply put - don't load those plugins! The plugins are found in the .soapuios/plugins
directory under the home directory
for the user (i.e. ~/
depending on your OS).
To disable loading of these plugins, rename the plugins
directory to something like disabled_plugins
. Easy. SoapUI will not be able to load these plugins now and the logs will no longer be filled with unnecessary exceptions!
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...