is it possible/is there an example to build a stateful service that exposes OData endpoint?
The point is to collect data in such a service and then expose the collection via OData endpoint
Regards,
Stefan
Sure, you can expose any kind of endpoint using whatever protocol or framework you want in a stateful service. I recommend using OData for Web API.
Here's an example project that uses Web API in a stateful service: https://github.com/Azure-Samples/service-fabric-dotnet-getting-started/tree/master/Services/WordCount/WordCount.Service
Related
I want to use OData as API-Gateway. Is it possible? Is there any example of OData that get rest request and use another service instead of entity framework provider?
I have some service that provide data and my services are using deferent type of databases SQL and NO-SQL. I want to use OData as a service provider of my architecture which my clients only see one endpoint and send OData requests then I can manage which service must response the request.
I searched and found there is some way to create custom provider for OData. Is there a way to use OData as API-Gateway?
When we are creating prototypes on Build we can consume OData service from Excel.
My doubt is if we can consume OData Gateway Service on Build? If it's possible, how can I do it?
Currently, it is not possible. All you can do is import the metadata as Edmx file and fill the mock data corresponding to that metadata.
There is an option;
You can also import objects from EDMX file (OData)
You can also try SAP Cloud Platform WebIDE. You can easily create a destination using your OData Gateway service and consume it via a template app.
Is it possible to consume WebAPi into windows service. Because WebAPI is http protocol, so iam not sure weather i will consume WebApi.
I tried search for consuming WebAPI with Windows service. I can't even find single examples.
Can any face similar kind of scenario
Yes we can able able to consume WebAPi inside the Windows service. Since it is windows based service we need consume it with HttpClient object.
I have recently discovered OData & the new WCF Web APi library on codeplex. The web api allows me to expose results as IQueryable, which allows me to expose URL's in the OData format. Myn question is what is the difference between this and a regular OData Service, I read the following blog post http://phejndorf.wordpress.com/2011/07/15/wcf-web-api-odata-format-doesnt-mean-odata-service/ but I am unsure what the OP means.
Thanks
The WCF Web API supports adding a [QueryComposition] attribute to a function so you can use the OData $filter=.. style of filtering data on the server and sending only a subset back to the client.
With OData, I should say WCF Data Services, there is much more that just querying. You can do all of the CRUD operations. It also means you are using the OData, is an AtomPub superset, protocol where with WCF Web API you do whatever you like. OData is actually a hypermedia format that contains metada, relations etc.
Is there a generic way of obtaining the service WSDL by using the service endpoint address. I know this can be done by appending ?wsdl to Axis2 services. But does this property hold for other web service containers as well?
?wsdl works for all web services. So you can follow it.