Does SoapUI works for WSHttpBinding WCF now?

Edit: I did notice that the basicHttpBinding was mentioned above, but now, there is an example to follow it.  Otherwise, please disregard this response. 

After having the same issue, I searched around and with a little trial and error I found what I would consider a work around perfect for a testing environment.  The work around solution is simple.  Change the binding from wsHttpBinding to basicHttpBinding.  Do this only for your testing environment.  Microsoft recommends the usage of wsHttpBinding and not the legacy basicHttpBinding.

In your app.config or web.config specify a new binding: 

<system.serviceModel>
  <bindings>
     <basicHttpBinding>
        <binding name="HTTPAccountServiceBinding" maxReceivedMessageSize="1000000"
                closeTimeout="00:02:00" sendTimeout="00:02:00">
        </binding>
      </basicHttpBinding>
  </bindings>

  <services>
      <service name="TestService" behaviorConfiguration="TestServiceBehavior">
        <host>
          <baseAddresses>
            <add baseAddress = "http://localhost:6000/TestService/" />
          </baseAddresses>
        </host>
        <endpoint address="" binding="basicHttpBinding" bindingConfiguration="HTTPAccountServiceBinding" contract="MyCompany.Service.ITestService">
          <identity>
            <dns value="localhost"/>
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
      </service>
    </services>
</system.serviceModel>

Anyways, thought I would share what got me into an appropriate testing situation.

Regards,
Chris Danielson