LHellstrom
17 years agoNew Contributor
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...
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...