Skip to content

Commit 13066a7

Browse files
davidlj95odrotbohm
authored andcommitted
Reintroduce link to "Understanding HATEOAS" document.
As the "understanding" section is not published any more, move link to Markdown file in the GitHub repository. Original ticket: DATAREST-1392. Fixes #356.
1 parent aea406c commit 13066a7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/main/asciidoc/repository-resources.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ If the configuration values (`RepositoryRestConfiguration.returnBodyOnUpdate` an
4242
[[repository-resources.resource-discoverability]]
4343
=== Resource Discoverability
4444

45-
A core principle of HATEOAS is that resources should be discoverable through the publication of links that point to the available resources. There are a few competing de-facto standards of how to represent links in JSON. By default, Spring Data REST uses https://tools.ietf.org/html/draft-kelly-json-hal[HAL] to render responses. HAL defines the links to be contained in a property of the returned document.
45+
A core principle of https://github.com/spring-guides/understanding/tree/master/hateoas[HATEOAS] is that resources should be discoverable through the publication of links that point to the available resources. There are a few competing de-facto standards of how to represent links in JSON. By default, Spring Data REST uses https://tools.ietf.org/html/draft-kelly-json-hal[HAL] to render responses. HAL defines the links to be contained in a property of the returned document.
4646

4747
Resource discovery starts at the top level of the application. By issuing a request to the root URL under which the Spring Data REST application is deployed, the client can extract, from the returned JSON object, a set of links that represent the next level of resources that are available to the client.
4848

0 commit comments

Comments
 (0)