From 8d1d5f97597ac9e037fcf5a1962af22ef0db9b2a Mon Sep 17 00:00:00 2001 From: Mattias Hellborg Arthursson Date: Mon, 21 Oct 2013 09:43:57 +0200 Subject: [PATCH] LDAP-266: Documentation --- src/docbkx/index.xml | 1 + src/docbkx/repositories.xml | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 src/docbkx/repositories.xml diff --git a/src/docbkx/index.xml b/src/docbkx/index.xml index 16d2bd1e..9c4d0e17 100644 --- a/src/docbkx/index.xml +++ b/src/docbkx/index.xml @@ -44,6 +44,7 @@ + diff --git a/src/docbkx/repositories.xml b/src/docbkx/repositories.xml new file mode 100644 index 00000000..46328f4c --- /dev/null +++ b/src/docbkx/repositories.xml @@ -0,0 +1,34 @@ + + + Spring LDAP Repositories + + + Overview + + + Spring LDAP has built-in support for Spring Data repositories. The basic functionality and configuration is described here. + When working with Spring LDAP repositories, please note the following: + + + Spring LDAP repositories can be enabled using an <ldap:repositories> tag in + your XML configuration or using an @EnableLdapRepositories annotation on a + configuration class. + + + All Spring LDAP repositories must work with entities annotated with the ODM annotations, as described + in . + + + 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 + SpringLdapRepository 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. + + + + +