Monday, June 13, 2011

soapUI and wsHttpBinding

Below are the steps required to allow soapUI to consume a WCF service which is using wsHttpBinding.

  1. By default Message Security is turned on for wsHttpBinding, which isn't supported by soapUI. So the security mode for the binding needs to be set to None:


    <bindings>
    <wsHttpBinding>
    <binding>
    <security mode="None">
    </security>
    </binding>
    </wsHttpBinding>
    </bindings>


  2. After creating the new soapUI project, the only update that is required is to select the 'Add default wsa:To' check box (as WS-Addressing is part of the wsHttpBinding). Enable/Disable WS-A addressing should already be selected, along with the appropriate SOAP action. The below options are available when you click the WS-A button, available as part of the Request window.


7 comments:

  1. Are you using the latest version of SOAPUI (4.0)? Is this the same issue in 4.0?

    ReplyDelete
  2. That worked perfectly. Thanks!

    ReplyDelete
  3. It worked great. Thanks.

    ReplyDelete
  4. Where to get the first step done?









    Where to change the binding? where is the binding file located?

    ReplyDelete
  5. Thanks for the nice post. It worked to me.

    ReplyDelete