From 4c434aab2bc6c7621c42ef769645a4a6b3bfe45b Mon Sep 17 00:00:00 2001 From: Oliver Drotbohm Date: Tue, 9 Jul 2019 13:05:15 +0200 Subject: [PATCH] #1016 - Polishing. Fixed link to the section on the EntityLinks interface from the section of the LinkRelationProvider documentation. --- src/main/asciidoc/server.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/server.adoc b/src/main/asciidoc/server.adoc index 06694aba1..b8e945c10 100644 --- a/src/main/asciidoc/server.adoc +++ b/src/main/asciidoc/server.adoc @@ -493,6 +493,6 @@ When building links, you usually need to determine the relation type to be used . If the type is annotated with `@Relation`, we use the values configured in the annotation. . If not, we default to the uncapitalized simple class name plus an appended `List` for the collection `rel`. . If the https://github.com/atteo/evo-inflector[EVO inflector] JAR is in the classpath, we use the plural of the single resource `rel` provided by the pluralizing algorithm. -. `@Controller` classes annotated with `@ExposesResourceFor` (see <> for details) transparently look up the relation types for the type configured in the annotation, so that you can use `LinkRelationProvider.getItemResourceRelFor(MyController.class)` and get the relation type of the domain type exposed. +. `@Controller` classes annotated with `@ExposesResourceFor` (see <> for details) transparently look up the relation types for the type configured in the annotation, so that you can use `LinkRelationProvider.getItemResourceRelFor(MyController.class)` and get the relation type of the domain type exposed. A `LinkRelationProvider` is automatically exposed as a Spring bean when you use `@EnableHypermediaSupport`. You can plug in custom providers by implementing the interface and exposing them as Spring beans in turn.