restful-architecture

I want to create a RAML validator that will get the RAML URLs resturn validation results. For that Im using raml-java-parser . As per its readme file I try to execute below line of code: String sourceUrl = "http://api.apihub.com/onpositive/api/espn-raml-api/espn.raml"; List<ValidationResult> results = RamlValidationService.createDefault().validate(sourceUrl); And get below error message: java.lang.NoSuchFieldError: VALUE Why I'm getting this error? Before that I got some class not found exceptions therefore I have applied below jar libraries manually. > juniversalchardet_1.0.3_1.0.0.jar > raml

Say I have two collection resources: /persons /organizations A GET to /persons/id/ returns a specific person. Likewise, a GET to /organizations/id returns a specific organization. A person can be member of one or more organizations. In this relation context, we have data such as the role of the person in the organization, the date on which the person joined the organization, ... Which of the designs make most sense? A membership resource /memberships/id , to which a GET returns the data of the relation context (together with a link to the person and the organization). A /persons/id

How to pass Query String Parameters in GET url using Rest Assured? URL is: http://example.com/building My Query Strings are : globalDates:{"startMs":1473672973818,"endMs":1481448973817,"period":90} limitTo:6 loadTvData:true startFrom:0 userId:5834fb36981baacb6a876427 You can pass them as a queryParam .. given() .queryParam("globalDates", "{\"startMs\":1473672973818,\"endMs\":1481448973817,\"period\":90}") .queryParam("startFrom", "0").queryParam("limitTo", "6").queryParam("loadTvData", true) .queryParam("startFrom", "0").queryParam("userId", "5834fb36981baacb6a876427") .when().get("http:/

I have a resource like this sales/customers/{customerno}. If a client sends a PUT request to this resource I would return 400 - Bad request if the xml in the entity body is not valid xml. But what if the xml is valid, but the content of the xml is not valid. Say for instance that the client is trying to update the customers PostCode and is providing a PostCode which is not valid. Is it correct to return 400 - Bad request in this case, or is it another http code I should have used? From Wikipedia's List of HTTP Status Codes : 400 Bad Request: The request cannot be fulfilled due to bad syntax.

Does ASP.NET MVC support RESTful architecture by default? What I want to know is, if I want to develop a RESTful kind of project, need I to specially work anything on ASP.NET MVC or it will support this feature by default? If you use Controllers to represent resources and simply implement "actions" that are equal to the HTTP methods, then you can produce a RESTful system very easily with ASP.NET MVC. MVC has been created with REST in mind. It is REST-friendly but not 100% REST compliant, especially when it comes to content-negotiation - although you can implement it yourself on the top of MVC

I have a simple RESTful method which currently returns JSON representation of an object. My question is more of from the architectural perspective and not completely technical. Should a RESTful service be designed in such a way that it returns both JSON and XML at the same time? As far as I know this is a bad practice and separate resources should be defined for this. One resource should return JSON data and other one XML. Am I thinking it correctly? The same resource may return either XML or JSON depending upon the request, but it shouldn't return both at the same time. You will know which