Forum Discussion
glamonta
15 years agoOccasional Contributor
Thanks again for additional information RJanecek.
I uploaded the Image of soapUI and the Missing Operation error at http://www.image-share.com/ijpg-994-273.html
I uploaded my navigator list in soapUI at http://www.image-share.com/ijpg-994-275.html
My project has the WSDL included above in it and the request used is above also. I don't see operation getEntitlementClassesForUser in my request, but I do see getEntitlementClassesForUserElement. The request comes from a consuming development group, and I'm running the tests against different testing environments. The WSDL used in the project comes from what the provider developers check into our configuration management repository.
This project has:
<con:interface ...>
...
<binding name="OC_UserEntitlementServiceSoapHttp" ...>
<operation name="getEntitlementClassesForUser">
...
</operation>
...
</binding>
...
</con:interface>
Thanks Vladimir, I'll send an e-mail to the address you mentioned above.
I uploaded the Image of soapUI and the Missing Operation error at http://www.image-share.com/ijpg-994-273.html
I uploaded my navigator list in soapUI at http://www.image-share.com/ijpg-994-275.html
My project has the WSDL included above in it and the request used is above also. I don't see operation getEntitlementClassesForUser in my request, but I do see getEntitlementClassesForUserElement. The request comes from a consuming development group, and I'm running the tests against different testing environments. The WSDL used in the project comes from what the provider developers check into our configuration management repository.
This project has:
<con:interface ...>
...
<binding name="OC_UserEntitlementServiceSoapHttp" ...>
<operation name="getEntitlementClassesForUser">
...
</operation>
...
</binding>
...
</con:interface>
Thanks Vladimir, I'll send an e-mail to the address you mentioned above.