There’s neither a REST nor a HATEOAS specification. Both are only concepts, or architectural styles, if you will. _embedded is part of the HAL format. It’s intended to embed (sic!) resources where otherwise only their URIs would be returned. For example GET http://localhost:8080/mywebservice/features is supposed to only return a list of URIs, like http://localhost:8080/mywebservice/features/GROUND, and … Read more
Spring HATEOAS provides common abstractions (representational models, a Link class, API to build links pointing to Spring MVC controllers, etc.) to ease building hypermedia driven REST APIs with Spring MVC in general. Thus, you can use it alongside Spring MVC to manually build those services. Spring Data REST uses Spring HATEOAS to automatically expose resources … Read more
There’s a lot of confusion about this, because most applications that call themselves REST don’t use hypermedia and aren’t REST at all. Hypermedia is a generalization of hypertext for content other than HTML. You can say hypertext is a subset of hypermedia. Hypermedia can be HTML in a browser, with all links, buttons and everything … Read more
The Serializer Bundle alone might not be enough for this situation as it is only concerned with serialization and deserialization, not more complex semantical tasks. I would suggest looking into FSCHateoasBundle to implement a pretty hypermedia format for your API.
The Serializer Bundle alone might not be enough for this situation as it is only concerned with serialization and deserialization, not more complex semantical tasks. I would suggest looking into FSCHateoasBundle to implement a pretty hypermedia format for your API.
That is a great question. If you look at the example for Hal you will see that the rels are defined within the context of the sub-resource. I do not know of any definitive guide on when the rel is related to the resource as a whole or a contained sub resource. The only extra … Read more
We’ve kind of half-done this on our current project. The representations we return are generated from domain objects, and the client can ask for them either in XML, JSON, or XHTML. If it’s an XHTML client like Firefox, then a person sees a set of outbound links from the well-known root resource and can browse … Read more
The Hypermedia Constraint (formerly known as HATEOAS) is a constraint that is used to provide direction to the user-agent. By including links in returned representations, the server can remove the burden from the user-agent of determining what actions can be taken based on the current application state and knowing who to interact with in-order to … Read more
This is definitely a tough nut to crack. At Google, we’ve implemented our Discovery Service that all our new APIs are built against. The TL;DR version is we generate a JSON Schema-like spec that our clients can parse – many of them dynamically. That results means easier SDK upgrades for the developer and easy/better maintenance … Read more
HATEOAS is a concept of application architecture. It defines the way in which application clients interact with the server, by navigating hypermedia links they find inside resource models returned by the server. To implement HATEOAS you need some standard way of representing resources, that will contain hypermedia information (links to related resources), for example, something … Read more