ClassNotFoundException after updating to SoapUI 5.2.0

Question

After having updated to SoapUI 5.2.0 I\'m getting

15:58:00,756 ERROR [SoapUI] An error occurred [com.eviware.soapui.plugins.auto.factories.AutoImportMethodFa         


        

Answer 1

I get same issue with Windows 5.2.1 x64 version. I tried copying the files from c:\user*YourUserName*.soapuios\plugins to /bin/ext but that did not fix it for me. I renamed the c:\user*YourUserName*.soapuios\plugins folder to c:\user*YourUserName*.soapuios\plugins.backup (so SOAP UI could not find it), restarted SUI, and now I don't get these errors. I presume I don't have access to the plugins, but I am not using those at the moment anyway.

I am not running under a Windows Administrator account, that could be relevant here.

Answer 2

I did run into same issue with Soap-Ui 5.2 (OpenSource, 64b, Windows) version. When using Testrunner, it gave the same error. I noticed that 5.2 has these new plugins added and they are installed to your profile folder, under c:\user\*YourUserName*\.soapuios\plugins. This folder holds these jar files: soapui-swagger-plugin-2.1.3-dist, ready-uxm-plugin-1.0.1-dist and ready-mqtt-plugin-dist.

Well, in my current project I have no use for those plugins so I just re-named the .soapuions folder to NOT.soapuios.

Then I re-launched testrunner from SoapUi and voila, there was no AutoImportMethodFactory error.

Ok, I am not sure if those plugins are the root cause but I think that it's not really a good idea that these kind of plugins are stored in windows User Profile -folder. eg. in Windows Server environment you have like 100 issues that can go wrong with that kind of setup :-)

Anyway, if someone knows how to rebase that plugins folder (I'd like to move it to same folder where Soapui is installed), I mean that is there a setting somewhere inside soapui that defines this folder, I would really appreciate that :-)

EDIT:

Just checked from 5.2 Release Notes (#### Released 2015-07-02 ####) from github and there is a bugfix mentioned: * SoapUI failed to load plugins when you run tests with testrunner.bat and the current directory differed from <SoapUI>\bin.

Answer 3

I ran into same issue and I also wanted to use swagger plugin. It got resolved when I ran the soapui with administrator access, so I think it has to do something to do with accessing and executing the required JAR files to load plugins.

Answer 4

You can resolve your issue (for any version of SoapUI listed above) by just renaming the original folder ‘plugins‘ to ‘plugins_NOTUsed‘ (or any other name of your choice). You might be thinking, by just renaming this folder how the actual problem has been solved – To explain this, it is just so that default plugins could be forced to be hidden during runtime and hence the problem doesn’t arise anymore.