I have a list of identical web api endpoints.
URL1/Products
URL2/Products
URL3/Products
......
The result of each of them is JSON (also identical)
I need to combine the results from each API in one "main" result.
How to consume web api list? And get combined result?
What approach should be used? Best practices?
Thanks.
P.S. ASP WebAPI, using now RestSharp as a client, .Net Framework 4.5.2
Related
I have some legacy applications that needs to call a new .net RESTFul API. What I am not sure of is if I can call a 4.51 API from a 2.0 web form.
For such a general question, I can give you a general answer.
Use HttpClient to make web requests to your REST API from your code behind, or make http requests from your javascript.
If you need to make requests to your REST API from your code behind, you will likely need JSON.NET to serialize the data from json to a .net object.
JSON.NET is available as a nuget package.
We have a web application using Jersey and Spring's rest template. Does anyone know of a tool that can scan a code base and produce a report that lists all exposed endpoints and also internal references to those endpoints?
You may also take a look at Swagger, a framework for describing, producing, consuming, and visualizing RESTful web services.
Swagger supports multiple REST frameworks and also JAX-RS based on Jersey.
From their GitHub Wiki:
The Swagger framework simultaneously addresses server, client, and documentation/sandbox needs for REST APIs. As a specification, it is language-agnostic. It also provides a long runway into new technologies and protocols beyond HTTP.
With Swagger's declarative resource specification, clients can understand and consume services without knowledge of server implementation or access to the server code. The Swagger UI framework allows both developers and non-developers to interact with the API in a sandbox UI that gives clear insight into how the API responds to parameters and options. Swagger happily speaks both JSON and XML, with additional formats in the works.
Jersey can provide a WADL report at the /application.wadl URI. It doesn't document complex types but at least gives you a list of endpoints.
See https://wikis.oracle.com/display/Jersey/WADL
I have been catching up with MVC4 Web API and WCF Data Service. From the surface, they both seem to be able to work with oData in the consuming client. I wonder which one is better for separation of concern (separate data service layer from UI layers). In my current solution, I have a plain MVC 3 style Intranet project and a MVC Data Service project. The 1st project has a Service Reference to the 2nd project. My goal is to write the data service once and make it available to all projects that would need to access underline database. When I read about Web API, it seems to me that the ApiControllers can return oData compliant result to the consuming client without MVC Data Service. My confusion is how I am going to expose this Web API MVC project as a service endpoint. Should I wrap it in WCF? Thanks.
You just create a controller inheriting ApiController and decorate one action with [Queryable] attribute, Rest depends on your route setup. Easy-Peasy.
Which one better? Web API. Since it has all the goodness of HTTP and you are not restricted to ATOM format.
You may use PocoHttp for seamless access of the data from your client.
In upgrading an old project that was built using WCF Web API to now use ASP.NET Web API, I have run into a few classes that implement HttpOperationHandler<HttpRequestMessage, T>. I'm unable to find an equivalent class in the new assemblies. Does something similar exist or will I need a different approach?
The concept of Operation handlers has been replaced with Filters and model binders.
Here are some links that you might find useful:
How to Migrate from WCF Web API to ASP.NET Web API
Mike's blog on How WebAPI does Parameter Binding
Getting started tutorials on ASP.NET WebAPI page.
Hope this helps.
I want to write a ruby web service client for a SOAP (JAX-WS) web service. I looked into soap4r and handsoap but couldn't find useful resources to write a (JAX-WS) client
Can you help me to find some resources and some way of doing it. Because as I can see, my web service is developed using oracle JDeveloper and looks little different than examples find in web.
I'm a beginner for SOAP, WSDL web services and finding it hard.
Has anyone done something like this before, or can you turn me to the correct direction?
JAX-WS is an API for the development of web services in Java. Know then that, in order to consume a SOAP/WSDL based web service, it is not necessary to know how that web service was implemented. It could be Java, .NET or any other number of languages. All that is required to create a SOAP based web service client is the WSDL for the service. It is self contained and self descriptive, including all operations and data types supported by the web service.
In order to familiarize yourself with web services, I would recommend trying to exercise some web services directly, for example using SoapUI. This will allow you to import a WSDL for an active web service, try out some of the operations, and see what the corresponding SOAP messages look like. Then, I would look at "What's the best way to use soap with ruby?" for more ruby specific approaches.