Hello Peeeetertje ,
I examined the classpath and noticed, that there are two versions of org.apache.xmlbeans.impl.xquery.saxon.XBeansXQuery, one with 3-paramters constructor in xmlbeans-xpath-2.6.0.jar and one with a 4-parameters constructor in xmlbeans-3.1.1-sb-fixed.jar.
According to the exception the latter one is intended to be used, while the first one comes first in the classpath.
It seems to me that xmlbeans-xpath-2.6.0.jar was accidentially packed into SoapUI 5.6.0 by SmartBear. There is only a single second class org.apache.xmlbeans.impl.xpath.saxon.XBeansXPath in that jar, but this seems to be identical to the version in xmlbeans-3.1.1-sb-fixed.jar.
My solution (macOS):
Works for me, no further sideeffects noticed so far.
cheers
I can confirm that Vienna20 workaround really works (remove the file xmlbeans-xpath-2.6.0.jar). It's been bugging me for a long time. I'm really surprised that Smartbear has not fixed it and released an updated version.
Hello pmerikan ,
thank you for your Kudo!
Actually someone having a support contract (a SoapUI license) could file a support request.
I don't have one.
Therefore I filed a bug on GitHub: https://github.com/SmartBear/soapui/issues/581
GitHub is not a replace for official support, but let's see what happens. 🙂
I doubt if Smartbear staff members are looking for bugs here in this forum.
cheers,
Harald
I can also confirm that Vienna20 solutions works well 🙂 I've been trying to solve it for weeks! Thanks!
