From 2945e9994f4bc21488f914aaa04920e038c0840d Mon Sep 17 00:00:00 2001 From: Amr Mostafa Date: Sun, 14 Dec 2014 13:49:53 +0200 Subject: [PATCH] #272 - Fix reference to non-existing interface in readme. Reference now mentions LinkDiscoverer instead of LinkProvider. --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index f2f45356..0d159be6 100644 --- a/readme.md +++ b/readme.md @@ -241,7 +241,7 @@ To enable the `ResourceSupport` subtypes be rendered according to the specificat * automatically picks up all `RelProvider` implementations in the `ApplicationContext` and bundles them into a `DelegatingRelProvider` available for autowiring. Registers providers to consider `@Relation` on domain types as well as Spring MVC controllers. If [EVO inflector](https://github.com/atteo/evo-inflector) is on the classpath collection rels are derived using the pluralizing algorithm implemented in the library (see [below](#relprovider-api)). ## LinkDiscoverer API -When working with hypermedia enabled representations, a common task is to find a link with a particular relation type in them. Spring HATEOAS provides [JSONPath](https://code.google.com/p/json-path/) based implementations of the `LinkProvider` interface for either the default representation rendering or HAL out of the box. When using `@EnableHypermediaSupport` we automatically expose an instance supporting the configured hypermedia type as Spring bean. +When working with hypermedia enabled representations, a common task is to find a link with a particular relation type in them. Spring HATEOAS provides [JSONPath](https://code.google.com/p/json-path/) based implementations of the `LinkDiscoverer` interface for either the default representation rendering or HAL out of the box. When using `@EnableHypermediaSupport` we automatically expose an instance supporting the configured hypermedia type as Spring bean. Alternatively you can simply setup and use an instance like this: