REST SOAP endpoints for a WCF service

Question

I have a WCF service and I want to expose it as both a RESTfull service and as a SOAP service   Anyone has done something like this before

User · Answer

If you only want to develop a single web service and have it hosted on many different endpoints (i.e. SOAP + REST, with XML, JSON, CSV, HTML outputes). You should also consider using ServiceStack which I've built for exactly this purpose where every service you develop is automatically available on on both SOAP and REST endpoints out-of-the-box without any configuration required.

The Hello World example shows how to create a simple with service with just (no config required):

public class Hello {
    public string Name { get; set; }
}

public class HelloResponse {
    public string Result { get; set; }
}

public class HelloService : IService
{
    public object Any(Hello request)
    {
        return new HelloResponse { Result = "Hello, " + request.Name };
    }
}

No other configuration is required, and this service is immediately available with REST in:

SOAP
XML
JSON
HTML

It also comes in-built with a friendly HTML output (when called with a HTTP client that has Accept:text/html e.g a browser) so you're able to better visualize the output of your services.

Handling different REST verbs are also as trivial, here's a complete REST-service CRUD app in 1 page of C# (less than it would take to configure WCF ;):

User · Answer

We must define the behavior configuration to REST endpoint   lt endpointBehaviors gt     lt behavior name  restfulBehavior  gt      lt webHttp defaultOutgoingResponseFormat  Json  defaultBodyStyle  Wrapped  automaticFormatSelectionEnabled  False    gt     lt  behavior gt   lt  endpointBehaviors gt    and also to a service          lt serviceBehaviors gt      lt behavior gt        lt serviceMetadata httpGetEnabled  true  httpsGetEnabled  true    gt         lt serviceDebug includeExceptionDetailInFaults  false    gt      lt  behavior gt   lt  serviceBehaviors gt    After the behaviors  next step is the bindings  For example basicHttpBinding to SOAP endpoint and webHttpBinding to REST    lt bindings gt      lt basicHttpBinding gt        lt binding name  soapService    gt      lt  basicHttpBinding gt      lt webHttpBinding gt        lt binding name  jsonp  crossDomainScriptAccessEnabled  true    gt      lt  webHttpBinding gt   lt  bindings gt    Finally we must define the 2 endpoint in the service definition  Attention for the address    of endpoint  where to REST service is not necessary nothing    lt services gt     lt service name  ComposerWcf ComposerService  gt       lt endpoint address    behaviorConfiguration  restfulBehavior  binding  webHttpBinding  bindingConfiguration  jsonp  name  jsonService  contract  ComposerWcf Interface IComposerService    gt       lt endpoint address  soap  binding  basicHttpBinding  name  soapService  contract  ComposerWcf Interface IComposerService    gt       lt endpoint address  mex  binding  mexHttpBinding  name  metadata  contract  IMetadataExchange    gt     lt  service gt   lt  services gt    In Interface of the service we define the operation with its attributes     namespace ComposerWcf Interface        ServiceContract      public interface IComposerService                OperationContract           WebInvoke Method    GET   UriTemplate     autenticationInfo  app id   access token    ResponseFormat   WebMessageFormat Json              RequestFormat   WebMessageFormat Json  BodyStyle   WebMessageBodyStyle Wrapped           Task lt UserCacheComplexType RootObject gt  autenticationInfo string app id  string access token             Joining all parties  this will be our WCF system serviceModel definition    lt system serviceModel gt      lt behaviors gt       lt endpointBehaviors gt         lt behavior name  restfulBehavior  gt           lt webHttp defaultOutgoingResponseFormat  Json  defaultBodyStyle  Wrapped  automaticFormatSelectionEnabled  False    gt         lt  behavior gt       lt  endpointBehaviors gt       lt serviceBehaviors gt         lt behavior gt           lt serviceMetadata httpGetEnabled  true  httpsGetEnabled  true    gt           lt serviceDebug includeExceptionDetailInFaults  false    gt         lt  behavior gt       lt  serviceBehaviors gt     lt  behaviors gt      lt bindings gt       lt basicHttpBinding gt         lt binding name  soapService    gt       lt  basicHttpBinding gt       lt webHttpBinding gt         lt binding name  jsonp  crossDomainScriptAccessEnabled  true    gt       lt  webHttpBinding gt     lt  bindings gt      lt protocolMapping gt       lt add binding  basicHttpsBinding  scheme  https    gt     lt  protocolMapping gt      lt serviceHostingEnvironment aspNetCompatibilityEnabled  true  multipleSiteBindingsEnabled  true    gt      lt services gt       lt service name  ComposerWcf ComposerService  gt         lt endpoint address    behaviorConfiguration  restfulBehavior  binding  webHttpBinding  bindingConfiguration  jsonp  name  jsonService  contract  ComposerWcf Interface IComposerService    gt         lt endpoint address  soap  binding  basicHttpBinding  name  soapService  contract  ComposerWcf Interface IComposerService    gt         lt endpoint address  mex  binding  mexHttpBinding  name  metadata  contract  IMetadataExchange    gt       lt  service gt     lt  services gt    lt  system serviceModel gt    To test the both endpoint  we can use WCFClient to SOAP and PostMan to REST

User · Answer

We must define the behavior configuration to REST endpoint   lt endpointBehaviors gt     lt behavior name  restfulBehavior  gt      lt webHttp defaultOutgoingResponseFormat  Json  defaultBodyStyle  Wrapped  automaticFormatSelectionEnabled  False    gt     lt  behavior gt   lt  endpointBehaviors gt    and also to a service          lt serviceBehaviors gt      lt behavior gt        lt serviceMetadata httpGetEnabled  true  httpsGetEnabled  true    gt         lt serviceDebug includeExceptionDetailInFaults  false    gt      lt  behavior gt   lt  serviceBehaviors gt    After the behaviors  next step is the bindings  For example basicHttpBinding to SOAP endpoint and webHttpBinding to REST    lt bindings gt      lt basicHttpBinding gt        lt binding name  soapService    gt      lt  basicHttpBinding gt      lt webHttpBinding gt        lt binding name  jsonp  crossDomainScriptAccessEnabled  true    gt      lt  webHttpBinding gt   lt  bindings gt    Finally we must define the 2 endpoint in the service definition  Attention for the address    of endpoint  where to REST service is not necessary nothing    lt services gt     lt service name  ComposerWcf ComposerService  gt       lt endpoint address    behaviorConfiguration  restfulBehavior  binding  webHttpBinding  bindingConfiguration  jsonp  name  jsonService  contract  ComposerWcf Interface IComposerService    gt       lt endpoint address  soap  binding  basicHttpBinding  name  soapService  contract  ComposerWcf Interface IComposerService    gt       lt endpoint address  mex  binding  mexHttpBinding  name  metadata  contract  IMetadataExchange    gt     lt  service gt   lt  services gt    In Interface of the service we define the operation with its attributes     namespace ComposerWcf Interface        ServiceContract      public interface IComposerService                OperationContract           WebInvoke Method    GET   UriTemplate     autenticationInfo  app id   access token    ResponseFormat   WebMessageFormat Json              RequestFormat   WebMessageFormat Json  BodyStyle   WebMessageBodyStyle Wrapped           Task lt UserCacheComplexType RootObject gt  autenticationInfo string app id  string access token             Joining all parties  this will be our WCF system serviceModel definition    lt system serviceModel gt      lt behaviors gt       lt endpointBehaviors gt         lt behavior name  restfulBehavior  gt           lt webHttp defaultOutgoingResponseFormat  Json  defaultBodyStyle  Wrapped  automaticFormatSelectionEnabled  False    gt         lt  behavior gt       lt  endpointBehaviors gt       lt serviceBehaviors gt         lt behavior gt           lt serviceMetadata httpGetEnabled  true  httpsGetEnabled  true    gt           lt serviceDebug includeExceptionDetailInFaults  false    gt         lt  behavior gt       lt  serviceBehaviors gt     lt  behaviors gt      lt bindings gt       lt basicHttpBinding gt         lt binding name  soapService    gt       lt  basicHttpBinding gt       lt webHttpBinding gt         lt binding name  jsonp  crossDomainScriptAccessEnabled  true    gt       lt  webHttpBinding gt     lt  bindings gt      lt protocolMapping gt       lt add binding  basicHttpsBinding  scheme  https    gt     lt  protocolMapping gt      lt serviceHostingEnvironment aspNetCompatibilityEnabled  true  multipleSiteBindingsEnabled  true    gt      lt services gt       lt service name  ComposerWcf ComposerService  gt         lt endpoint address    behaviorConfiguration  restfulBehavior  binding  webHttpBinding  bindingConfiguration  jsonp  name  jsonService  contract  ComposerWcf Interface IComposerService    gt         lt endpoint address  soap  binding  basicHttpBinding  name  soapService  contract  ComposerWcf Interface IComposerService    gt         lt endpoint address  mex  binding  mexHttpBinding  name  metadata  contract  IMetadataExchange    gt       lt  service gt     lt  services gt    lt  system serviceModel gt    To test the both endpoint  we can use WCFClient to SOAP and PostMan to REST

User · Answer

MSDN seems to have an article for this now    https   msdn microsoft com en-us library bb412196 v vs 110  aspx  Intro       By default  Windows Communication Foundation  WCF  makes endpoints available only to SOAP clients  In How to  Create a Basic WCF Web HTTP Service  an endpoint is made available to non-SOAP clients  There may be times when you want to make the same contract available both ways  as a Web endpoint and as a SOAP endpoint  This topic shows an example of how to do this

User · Answer

This is what i did to make it work  Make sure you put webHttp automaticFormatSelectionEnabled  true  inside endpoint behaviour    ServiceContract  public interface ITestService         WebGet BodyStyle   WebMessageBodyStyle Bare  UriTemplate     product   ResponseFormat   WebMessageFormat Json       string GetData       public class TestService   ITestService       public string GetJsonData                 return  I am good                Inside service model      lt service name  TechCity Business TestService  gt        lt endpoint address  soap  binding  basicHttpBinding  name  SoapTest        bindingName  BasicSoap  contract  TechCity Interfaces ITestService    gt       lt endpoint address  mex                contract  IMetadataExchange  binding  mexHttpBinding   gt       lt endpoint behaviorConfiguration  jsonBehavior  binding  webHttpBinding                name  Http  contract  TechCity Interfaces ITestService    gt       lt host gt         lt baseAddresses gt           lt add baseAddress  http   localhost 8739 test    gt         lt  baseAddresses gt       lt  host gt     lt  service gt    EndPoint Behaviour     lt endpointBehaviors gt       lt behavior name  jsonBehavior  gt         lt webHttp automaticFormatSelectionEnabled  true     gt         lt  -- use JSON serialization -- gt       lt  behavior gt     lt  endpointBehaviors gt

User · Answer

If you only want to develop a single web service and have it hosted on many different endpoints (i.e. SOAP + REST, with XML, JSON, CSV, HTML outputes). You should also consider using ServiceStack which I've built for exactly this purpose where every service you develop is automatically available on on both SOAP and REST endpoints out-of-the-box without any configuration required.

The Hello World example shows how to create a simple with service with just (no config required):

public class Hello {
    public string Name { get; set; }
}

public class HelloResponse {
    public string Result { get; set; }
}

public class HelloService : IService
{
    public object Any(Hello request)
    {
        return new HelloResponse { Result = "Hello, " + request.Name };
    }
}

No other configuration is required, and this service is immediately available with REST in:

SOAP
XML
JSON
HTML

It also comes in-built with a friendly HTML output (when called with a HTTP client that has Accept:text/html e.g a browser) so you're able to better visualize the output of your services.

Handling different REST verbs are also as trivial, here's a complete REST-service CRUD app in 1 page of C# (less than it would take to configure WCF ;):

User · Answer

This post has already a very good answer by  Community wiki  and I also recommend to look at Rick Strahl s Web Blog  there are many good posts about WCF Rest like this   I used both to get this kind of MyService-service    Then I can use the REST-interface from jQuery or SOAP from Java   This is from my Web Config    lt system serviceModel gt    lt services gt     lt service name  MyService  behaviorConfiguration  MyServiceBehavior  gt      lt endpoint name  rest  address    binding  webHttpBinding  contract  MyService  behaviorConfiguration  restBehavior   gt      lt endpoint name  mex  address  mex  binding  mexHttpBinding  contract  MyService   gt      lt endpoint name  soap  address  soap  binding  basicHttpBinding  contract  MyService   gt     lt  service gt    lt  services gt    lt behaviors gt     lt serviceBehaviors gt      lt behavior name  MyServiceBehavior  gt       lt serviceMetadata httpGetEnabled  true   gt       lt serviceDebug includeExceptionDetailInFaults  true    gt      lt  behavior gt     lt  serviceBehaviors gt     lt endpointBehaviors gt      lt behavior name  restBehavior  gt       lt webHttp  gt      lt  behavior gt     lt  endpointBehaviors gt    lt  behaviors gt   lt  system serviceModel gt    And this is my service-class   svc-codebehind  no interfaces required             lt summary gt  MyService documentation here     lt  summary gt   ServiceContract Name    MyService   Namespace    http   myservice    SessionMode   SessionMode NotAllowed      ServiceKnownType typeof  IList lt MyDataContractTypes gt      ServiceBehavior Name    MyService   Namespace    http   myservice     public class MyService        OperationContract Name    MyResource1         WebGet ResponseFormat   WebMessageFormat Xml  UriTemplate    MyXmlResource  key         public string MyResource1 string key                return  Test      key              OperationContract Name    MyResource2         WebGet ResponseFormat   WebMessageFormat Json  UriTemplate    MyJsonResource  key         public string MyResource2 string key                return  Test      key            Actually I use only Json or Xml but those both are here for a demo purpose  Those are GET-requests to get data  To insert data I would use method with attributes    OperationContract Name    MyResourceSave     WebInvoke Method    POST   ResponseFormat   WebMessageFormat Json  UriTemplate    MyJsonResource    public string MyResourceSave string thing

User · Answer

MSDN seems to have an article for this now    https   msdn microsoft com en-us library bb412196 v vs 110  aspx  Intro       By default  Windows Communication Foundation  WCF  makes endpoints available only to SOAP clients  In How to  Create a Basic WCF Web HTTP Service  an endpoint is made available to non-SOAP clients  There may be times when you want to make the same contract available both ways  as a Web endpoint and as a SOAP endpoint  This topic shows an example of how to do this

User · Answer

This post has already a very good answer by  Community wiki  and I also recommend to look at Rick Strahl s Web Blog  there are many good posts about WCF Rest like this   I used both to get this kind of MyService-service    Then I can use the REST-interface from jQuery or SOAP from Java   This is from my Web Config    lt system serviceModel gt    lt services gt     lt service name  MyService  behaviorConfiguration  MyServiceBehavior  gt      lt endpoint name  rest  address    binding  webHttpBinding  contract  MyService  behaviorConfiguration  restBehavior   gt      lt endpoint name  mex  address  mex  binding  mexHttpBinding  contract  MyService   gt      lt endpoint name  soap  address  soap  binding  basicHttpBinding  contract  MyService   gt     lt  service gt    lt  services gt    lt behaviors gt     lt serviceBehaviors gt      lt behavior name  MyServiceBehavior  gt       lt serviceMetadata httpGetEnabled  true   gt       lt serviceDebug includeExceptionDetailInFaults  true    gt      lt  behavior gt     lt  serviceBehaviors gt     lt endpointBehaviors gt      lt behavior name  restBehavior  gt       lt webHttp  gt      lt  behavior gt     lt  endpointBehaviors gt    lt  behaviors gt   lt  system serviceModel gt    And this is my service-class   svc-codebehind  no interfaces required             lt summary gt  MyService documentation here     lt  summary gt   ServiceContract Name    MyService   Namespace    http   myservice    SessionMode   SessionMode NotAllowed      ServiceKnownType typeof  IList lt MyDataContractTypes gt      ServiceBehavior Name    MyService   Namespace    http   myservice     public class MyService        OperationContract Name    MyResource1         WebGet ResponseFormat   WebMessageFormat Xml  UriTemplate    MyXmlResource  key         public string MyResource1 string key                return  Test      key              OperationContract Name    MyResource2         WebGet ResponseFormat   WebMessageFormat Json  UriTemplate    MyJsonResource  key         public string MyResource2 string key                return  Test      key            Actually I use only Json or Xml but those both are here for a demo purpose  Those are GET-requests to get data  To insert data I would use method with attributes    OperationContract Name    MyResourceSave     WebInvoke Method    POST   ResponseFormat   WebMessageFormat Json  UriTemplate    MyJsonResource    public string MyResourceSave string thing

User · Answer

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   lt endpointBehaviors gt     lt behavior name  jsonBehavior  gt       lt enableWebScript  gt     lt  behavior gt   lt  endpointBehaviors gt    An example of endpoint configuration in your scenario is    lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  json  binding  webHttpBinding   behaviorConfiguration  jsonBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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   lt behavior name  poxBehavior  gt     lt webHttp  gt   lt  behavior gt    Endpoints   lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  xml  binding  webHttpBinding   behaviorConfiguration  poxBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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      lt client gt       lt endpoint address  http   www example com soap  binding  basicHttpBinding        contract  ITestService  name  BasicHttpBinding ITestService    gt     lt  client gt    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

User · Answer

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   lt endpointBehaviors gt     lt behavior name  jsonBehavior  gt       lt enableWebScript  gt     lt  behavior gt   lt  endpointBehaviors gt    An example of endpoint configuration in your scenario is    lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  json  binding  webHttpBinding   behaviorConfiguration  jsonBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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   lt behavior name  poxBehavior  gt     lt webHttp  gt   lt  behavior gt    Endpoints   lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  xml  binding  webHttpBinding   behaviorConfiguration  poxBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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      lt client gt       lt endpoint address  http   www example com soap  binding  basicHttpBinding        contract  ITestService  name  BasicHttpBinding ITestService    gt     lt  client gt    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

User · Answer

This is what i did to make it work  Make sure you put webHttp automaticFormatSelectionEnabled  true  inside endpoint behaviour    ServiceContract  public interface ITestService         WebGet BodyStyle   WebMessageBodyStyle Bare  UriTemplate     product   ResponseFormat   WebMessageFormat Json       string GetData       public class TestService   ITestService       public string GetJsonData                 return  I am good                Inside service model      lt service name  TechCity Business TestService  gt        lt endpoint address  soap  binding  basicHttpBinding  name  SoapTest        bindingName  BasicSoap  contract  TechCity Interfaces ITestService    gt       lt endpoint address  mex                contract  IMetadataExchange  binding  mexHttpBinding   gt       lt endpoint behaviorConfiguration  jsonBehavior  binding  webHttpBinding                name  Http  contract  TechCity Interfaces ITestService    gt       lt host gt         lt baseAddresses gt           lt add baseAddress  http   localhost 8739 test    gt         lt  baseAddresses gt       lt  host gt     lt  service gt    EndPoint Behaviour     lt endpointBehaviors gt       lt behavior name  jsonBehavior  gt         lt webHttp automaticFormatSelectionEnabled  true     gt         lt  -- use JSON serialization -- gt       lt  behavior gt     lt  endpointBehaviors gt

User · Answer

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   lt endpointBehaviors gt     lt behavior name  jsonBehavior  gt       lt enableWebScript  gt     lt  behavior gt   lt  endpointBehaviors gt    An example of endpoint configuration in your scenario is    lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  json  binding  webHttpBinding   behaviorConfiguration  jsonBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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   lt behavior name  poxBehavior  gt     lt webHttp  gt   lt  behavior gt    Endpoints   lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  xml  binding  webHttpBinding   behaviorConfiguration  poxBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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      lt client gt       lt endpoint address  http   www example com soap  binding  basicHttpBinding        contract  ITestService  name  BasicHttpBinding ITestService    gt     lt  client gt    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

User · Answer

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   lt endpointBehaviors gt     lt behavior name  jsonBehavior  gt       lt enableWebScript  gt     lt  behavior gt   lt  endpointBehaviors gt    An example of endpoint configuration in your scenario is    lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  json  binding  webHttpBinding   behaviorConfiguration  jsonBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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   lt behavior name  poxBehavior  gt     lt webHttp  gt   lt  behavior gt    Endpoints   lt services gt     lt service name  TestService  gt       lt endpoint address  soap  binding  basicHttpBinding  contract  ITestService   gt       lt endpoint address  xml  binding  webHttpBinding   behaviorConfiguration  poxBehavior  contract  ITestService   gt     lt  service gt   lt  services gt    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      lt client gt       lt endpoint address  http   www example com soap  binding  basicHttpBinding        contract  ITestService  name  BasicHttpBinding ITestService    gt     lt  client gt    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

[wcf] REST / SOAP endpoints for a WCF service

Examples related to wcf

Examples related to rest

Examples related to soap