Forum Discussion
Hi
I don't understand why this is off topic SoapUI. I have documented an odd behavior using SoapUI, where SoapUI does work running in one mode, and doing exactly the same thing is not working running in another mode. To me it seems like som sort of bug og at least an undocumented difference between running a SoapUI test from the UI and running it using the testrunner script.
Regards,
Rune
- nmrao7 years agoChampion Level 3Because, in the exception, no where it seen the soapui package name such as "com.eviware.*"
- nmrao7 years agoChampion Level 3By the way, it is not confirmed in your reply anything on the other suggestions. Have you tried any?
- tempo667 years agoOccasional Contributor
First of all I didn't post the entire exception. But I'll do that.
Regarding suggestions. Do you mean looking on the net? I'm very well aware of the meaning of the exception, and yes I did look on the net. But since my groovy plugin work well when running the test from the SoapUI GUI I assume the problem is around testrunner.sh not being able to load the plugin dependent libraries properly. Any other ideas?
/Rune
- nmrao7 years agoChampion Level 3Ok.
When you say, "when running the test from the SoapUI GUI", how are you using your custom jar file? In a script?
Related Content
Recent Discussions
- 15 years ago