I have a WCF RIA service, a silverlight application and I should also support other kinds of application like WPF and others. By default, the SL app uses binary over http for communication with the service. Is it possible to expose a SOAP endpoint for the RIA service so that non SL applications can consume the service via SOAP endpoint ?
It is possible to expose RIA service via SOAP.
By adding below line to the configuration file it is possible to expose SOAP end point for RIA services
<add name="Soap" type="Microsoft.ServiceModel.DomainServices.Hosting.SoapXmlEndpointFactory, Microsoft.ServiceModel.DomainServices.Hosting, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
Reference.
http://blogs.msdn.com/b/davrous/archive/2010/12/03/how-to-open-a-wcf-ria-services-application-to-other-type-of-clients-the-soap-endpoint-3-5.aspx
Disclaimer - I haven't implemented it.
Related
my question is this:
Does WCF(Windows Communication Foundation) have a Micro Web Service feature?And does it only supported by REST?
Check this out: Difference between WCF and Web API and WCF REST and Web Service
Why you want to use WCF for REST service when you can use Web API? Is there something reasonable?
I am new to altova mapforce. I wanted to know that does Altova Mapforce exposes any kind of REST APIS so that we can supply it the input from a single page web application and get the data from the tool back in any format(JSON,XML)?
MapForce version 2022 rel 2 still can't expose REST services, only SOAP.
The SOAP service has to be compiled in an ASPX app and run on IIS.
It can consume REST and SOAP services.
You can create a REST service with the FlowForce/MapForce servers.
However ist does not support CORS.
It wouldn't work with a Single Page Web App.
When you create owin hosted API controller in service fabric with vs 2015, the following line appears in the ServiceManifest.xml file (under Resources/Endpoints):
<Endpoint Protocol="http" Name="ServiceEndpoint" Type="Input" Port="8726" />
But in case of regular stateless service, the following line appears in the related ServiceManifest.xml file:
<Endpoint Name="ServiceEndpoint" />
Since both are stateless services under the hood, why the difference in Endpoint definition? What does this signify? Also how would I call the 2nd service (from 1st service) over http transport?
Thanks.
A web API is normally used as a gateway to the application, so it requires a fixed port, to be mapped by the load balancer to an external port (in contrast to the default, a random port assigned by the Fabric).
In addition, this ensures a correct HTTP endpoint registration in Windows, as described in the documentation:
This step is important because the service host process runs under
restricted credentials (Network Service on Windows). This means that
your service won't have access to set up an HTTP endpoint on its own.
By using the endpoint configuration, Service Fabric knows to set up
the proper access control list (ACL) for the URL that the service will
listen on. Service Fabric also provides a standard place to configure
endpoints.
I have a requirement to implement a serial web service call to 2 web services, say ServiceA followed by ServiceB. I implemented this using xml, having two separated gateways for each service and all, I wanted to know how to do this using annotation. How will I mention which service activator goes with which gateway.
Thanks
.NET RIA Services work with an HTTP binding. What about TCP or named pipes?
WCF Named pipes don't work outside of a single machine so they don't count in the case of Rich Internet Applications. Not sure about net.tcp
Net.Tcp does work as far as I know. – the_drow
No, according to it's program manager, Dinesh Kulkarni it's impossible. WCF RIA over Net.TCP binding?