Forum Discussion

LHellstrom's avatar
LHellstrom
New Contributor
17 years ago

Failed to find matching operation

We just experienced a strange bug.
Our wsdl file which we base the project on contains two port-types (A and B) which have identically named operations ( C ).
We set up a MockService with a MockOperation of C based on the binding (Ab) that refers to port-type A.
When our client sends the request aimed for operation C, we get "Failed to find matching operation for request" error in soapUI. (See attached log-file)

BUT, if we add another MockOperation to the MockService, this one based on binding B and mocking its operation C, the request is received by this mock!

What is happening? I can't figure out anything in the request that indicates a certain binding/interface, only the  service-name and operation-name...

2 Replies

  • omatzura's avatar
    omatzura
    Super Contributor
    Hi!

    that does sound strange!

    Have you tried toggling the require SOAP Action / Version settings for the MockService to see if it makes any difference (bottom left properties)

    Can you share your wsdl/soapUI project so I can debug this locally? (mail to ole@eviware.com)

    regards,

    /Ole
    eviware.com