From b9ce3e786d593592b41f84f6e6f7958e9ae5716a Mon Sep 17 00:00:00 2001 From: Juraj Martinka Date: Wed, 8 Mar 2017 14:46:12 +0100 Subject: [PATCH] DATALDAP-25 - Fix link to spring-ldap docs in reference documentation. Remove superfluous .RELEASE from spring-ldap documentation link. Original pull request: #1. --- src/main/asciidoc/reference/ldap-repositories.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/asciidoc/reference/ldap-repositories.adoc b/src/main/asciidoc/reference/ldap-repositories.adoc index 449691e7..17a667b0 100644 --- a/src/main/asciidoc/reference/ldap-repositories.adoc +++ b/src/main/asciidoc/reference/ldap-repositories.adoc @@ -8,7 +8,7 @@ This chapter will point out the specialties for repository support for LDAP. Thi * Spring LDAP repositories can be enabled using an `` tag in your XML configuration or using an `@EnableLdapRepositories` annotation on a configuration class. * To include support for `LdapQuery` parameters in automatically generated repositories, have your interface extend `LdapRepository` rather than `CrudRepository`. -* All Spring LDAP repositories must work with entities annotated with the ODM annotations, as described in http://docs.spring.io/spring-ldap/docs/{springLdapVersion}.RELEASE/reference/#odm[Object-Directory Mapping]. +* All Spring LDAP repositories must work with entities annotated with the ODM annotations, as described in http://docs.spring.io/spring-ldap/docs/{springLdapVersion}/reference/#odm[Object-Directory Mapping]. * Since all ODM managed classes must have a Distinguished Name as ID, all Spring LDAP repositories must have the ID type parameter set to `javax.naming.Name`. Indeed, the built-in `LdapRepository` only takes one type parameter; the managed entity class, defaulting ID to `javax.naming.Name`. * Due to specifics of the LDAP protocol, paging and sorting is not supported for Spring LDAP repositories. @@ -225,7 +225,7 @@ public interface PersonRepository extends PagingAndSortingRepository