LHellstrom
New Contributor
Joined 17 years ago
User Profile
User Widgets
Contributions
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...3.1KViews0likes2CommentsNullPointerException in hideContent
Hi, when creating a Request with default values from a standardized schema, we get a NullPointerException in soapUI, and only one of two mandatory parameters show up in the request xml. The request we're trying to create is the AnswerCall from this xsd: http://www.ecma-international.org/stand ... r-call.xsd The ConnectionID parameter (that is causing the failure) is defined here: http://www.ecma-international.org/stand ... ifiers.xsd2.3KViews0likes1CommentRe: Relative paths in project files
I just want to add my vote to this feature request. Being able to share a soapUI project between members, by having the project stored in the version control system in a team is essential for us. And to be able to do that, the path to the wsdl must be relative to the project file, it seems.1.3KViews0likes0Comments