WCF client talk to soapUI mock service using wsHttpBinding
-
Hi, I'm testing a WCF client application using wsHttpBinding. I use soapUI to create a mock service using the existing WSDL. I'm struggling to get them correctly to communicate to each other. When the WCF client calls to soapUI's mock service, the soapUI mock service throws exception which I can see it in soapUI's error log:
ERROR:com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [null] and body element [{http://tempuri.org/}UnitLocation] with SOAP Version [SOAP 1.2]
So soapUI thought the call from WCF client had wrong soapAction, but when using Service Trace Viewer to check the soap1.2 Message, the soapAction looks fine to me:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/IMobilityInboundService/UnitLocation</a:Action>
<a:MessageID>urn:uuid:e1b3753c-603a-422c-a81e-3d524f4a86b7</a:MessageID>
<ActivityId CorrelationId="f538e84f-2ed1-411a-8e0f-f19c1dbf2446" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">55a95dee-7d91-450c-917c-0a59177d95ee</ActivityId>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">http://127.0.0.1:8088/mockWSHttpBinding\_IMobilityInboundService</a:To>
</s:Header>If changing to use basicHttpBinding and based on it generate a new soapUI mock service, it's fine. Anyone has successful experience to communicate with soapUI mock service using wsHttpBinding, can be willing to give details on how to set soapUI properly. I know compared to basicHttpBinding, wsHttpBinding will have more involvement. Thanks very much.
-
Hi, I'm testing a WCF client application using wsHttpBinding. I use soapUI to create a mock service using the existing WSDL. I'm struggling to get them correctly to communicate to each other. When the WCF client calls to soapUI's mock service, the soapUI mock service throws exception which I can see it in soapUI's error log:
ERROR:com.eviware.soapui.impl.wsdl.mock.DispatchException: Missing operation for soapAction [null] and body element [{http://tempuri.org/}UnitLocation] with SOAP Version [SOAP 1.2]
So soapUI thought the call from WCF client had wrong soapAction, but when using Service Trace Viewer to check the soap1.2 Message, the soapAction looks fine to me:
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/IMobilityInboundService/UnitLocation</a:Action>
<a:MessageID>urn:uuid:e1b3753c-603a-422c-a81e-3d524f4a86b7</a:MessageID>
<ActivityId CorrelationId="f538e84f-2ed1-411a-8e0f-f19c1dbf2446" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">55a95dee-7d91-450c-917c-0a59177d95ee</ActivityId>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">http://127.0.0.1:8088/mockWSHttpBinding\_IMobilityInboundService</a:To>
</s:Header>If changing to use basicHttpBinding and based on it generate a new soapUI mock service, it's fine. Anyone has successful experience to communicate with soapUI mock service using wsHttpBinding, can be willing to give details on how to set soapUI properly. I know compared to basicHttpBinding, wsHttpBinding will have more involvement. Thanks very much.
its possible to test a WCF Service with Wshttp bindings in SOAP UI. Please follow the steps as mentioned below: In SOAP UI Check Whether WS-A is enabled. Trigger a request in SOAP UI...U will get the corresponding response... :) Note:If you get a response like SOAP Action mismatch occured, just enable Ws reliable messaging , trigger a req, then , disable the same & trigger a req.It will work.... This is Applicable to SOAPUI 3.0.1 Regards, Jay +919972588344
-
its possible to test a WCF Service with Wshttp bindings in SOAP UI. Please follow the steps as mentioned below: In SOAP UI Check Whether WS-A is enabled. Trigger a request in SOAP UI...U will get the corresponding response... :) Note:If you get a response like SOAP Action mismatch occured, just enable Ws reliable messaging , trigger a req, then , disable the same & trigger a req.It will work.... This is Applicable to SOAPUI 3.0.1 Regards, Jay +919972588344