Php – WSDL URL for a WCF Service (basicHttpBinding) hosted inside a Windows Service

You can expose the service in two different endpoints. the SOAP one can use the binding that support SOAP e.g. basicHttpBinding, the RESTful one can use the webHttpBinding. I assume your REST service will be in JSON, in that case, you need to configure the two endpoints with the following behaviour configuration

<endpointBehaviors>
  <behavior name="jsonBehavior">
    <enableWebScript/>
  </behavior>
</endpointBehaviors>

An example of endpoint configuration in your scenario is

<services>
  <service name="TestService">
    <endpoint address="soap" binding="basicHttpBinding" contract="ITestService"/>
    <endpoint address="json" binding="webHttpBinding"  behaviorConfiguration="jsonBehavior" contract="ITestService"/>
  </service>
</services>

so, the service will be available at

• http://www.example.com/soap
• http://www.example.com/json

Apply [WebGet] to the operation contract to make it RESTful. e.g.

public interface ITestService
{
   [OperationContract]
   [WebGet]
   string HelloWorld(string text)
}

Note, if the REST service is not in JSON, parameters of the operations can not contain complex type.

Reply to the post for SOAP and RESTful POX(XML)

For plain old XML as return format, this is an example that would work both for SOAP and XML.

[ServiceContract(Namespace = "http://test")]
public interface ITestService
{
    [OperationContract]
    [WebGet(UriTemplate = "accounts/{id}")]
    Account[] GetAccount(string id);
}

POX behavior for REST Plain Old XML

<behavior name="poxBehavior">
  <webHttp/>
</behavior>

Endpoints

<services>
  <service name="TestService">
    <endpoint address="soap" binding="basicHttpBinding" contract="ITestService"/>
    <endpoint address="xml" binding="webHttpBinding"  behaviorConfiguration="poxBehavior" contract="ITestService"/>
  </service>
</services>

Service will be available at

• http://www.example.com/soap
• http://www.example.com/xml

REST request try it in browser,

http://www.example.com/xml/accounts/A123

SOAP request client endpoint configuration for SOAP service after adding the service reference,

  <client>
    <endpoint address="http://www.example.com/soap" binding="basicHttpBinding"
      contract="ITestService" name="BasicHttpBinding_ITestService" />
  </client>

in C#

TestServiceClient client = new TestServiceClient();
client.GetAccount("A123");

Another way of doing it is to expose two different service contract and each one with specific configuration. This may generate some duplicates at code level, however at the end of the day, you want to make it working.

Well, I still can't get it to work on the Vista servers - it's still giving 503 errors, but I ended up getting it setup on a Windows 2003 server, and it seems to be working now.

One thing I did learn in this process was the use of HttpCfg.exe to allow a user to open a non-standard HTTP port.

Basically I had to run something like the following command:

httpcfg.exe set urlacl /u http://+:5555/ /a "O:AOG:DAD:(A;;RPWPCCDCLCSWRCWDWOGA;;;S-1-0-0)"

You can then view the URL ACL settings with this command:

httpcfg.exe query urlacl

On Vista, you can run the same types of commands using netsh (see link below).

Sadly, this took awhile to figure out, but it was a good learning experience.

Here are some links that I thought were useful in figuring this out:

• http://www.leastprivilege.com/HttpCfgACLHelper.aspx
  • This explians how to get the SID for your user account (for the /a part of the command. Coincidentally, this is easier on Vista - you can just specify the domain\user in the netsh http set urlacl command
• http://technet.microsoft.com/en-us/library/cc781601.aspx
  • This explains the syntax/options of the HttpCfg.exe command
• http://msdn.microsoft.com/en-us/library/ms733768.aspx
  • This really explains everything you need to know for HttpCfg/netsh http
• http://blogs.msdn.com/drnick/archive/2006/04/14/configuring-http.aspx
  • Similar info to the msdn link above, but provides more explanation, and more relation to WCF
• http://dotnet.dzone.com/news/msmq-wcf-and-iis-getting-them-
  • Another description of WCF and HTTP (and MSMQ), with a focus on IIS