Forum Discussion

nad101's avatar
Occasional Visitor
10 years ago




I'm getting this lovely little error running a MockService that attempts to decrypt incoming data. The full cause stack trace is below. I'm using SoapUI 5.0.0. I'm pretty certain it's a soapui issue - I can recreate it with both the client and server in SoapUI - but I could do with a sanity check.


A quick overview of the setup:

  • I have 2 keystores, one with a private key and one with the corresponding public key.
  • Create a "server" project; import a wsdl and create a mock service.
  • Create an incoming WS-Security config  on the project using the private key.
  • Change the mock service properties to use this as the Incoming WSS
  • Create a second project using the same wsdl
  • Create an outbound WS-Security config on the project using the public key to encrypt all or part of the message
  • Create a request; set up authorization and set it to use this as the Outgoing WSS.


So, this is about the simplest WS-Security setup I can think of... Surely someone else must have seen this?






Caused by: java.lang.NoSuchMethodError:
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRequest.initPostRequest(
at com.eviware.soapui.impl.wsdl.mock.WsdlMockRequest.<init>(
at com.eviware.soapui.impl.wsdl.mock.WsdlMockDispatcher.dispatchRequest(


What I think is happening - XMLCipher is part of apache santuario (AKA xmlsec) and ReferenceListProcessor is part of apache wss4j - looking at the pom files, SoapUI appears to be using wss4j 1.6.14 and xmlsec 1.4.5 but that version of wss4j  requires xmlsec 1.5.6.


1 Reply

  • The fix for me was to add an xml-security dependency to the soapui maven plugin like so:

    <!-- To run, enter this command from the module directory:  mvn soapui:test -->

    In my case, I didn't have an xml security dependency anywhere else in my project.


    In other cases, it seems like some may be experiencing this error due to having multiple xml security dependencies throughout their project (and they are conflicting). So, if the above fix doesn't work for you in that scenario, you may need to look into which depedencies in your project are including xml security and deciding which one you want to include and which one you want to exclude (using maven's exclusion or provided markings in the given pom).