New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDAP-319: add pagination support to LdapRepository #354
Comments
Rob Winch said: The reference states
but I'm not familiar with the history of this. Perhaps [~ marthursson] can elaborate |
Mattias Hellborg Arthursson said: The problem with pagination in LDAP is that you need to re-use the exact same connection for each pagination request, or else the pagination control becomes invalid. This means that pagination like you're used to with "real" databases (as it is normally done in Spring repositories, using As described in the [reference section on paged results | http://docs.spring.io/spring-ldap/docs/2.0.2.RELEASE/reference/#paged-search-results], the problem with re-using the same connection can be managed by wrapping all the pagination calls using |
Rob Winch said: Thanks for the response marthursson! What if we were able to include information in the response that could be passed in as an argument (similar to what page we are requesting)? Would that work? |
I'm facing OperationNotSupportedException: [LDAP: error code 12 - 00000057: LdapErr: DSID-0C090B0B, comment: Error processing control, data 0, v3839 ]; remaining name |
I have implemented this recently with pure JNDI and it worked for me with Active Directory and DirX. Does your directory server support this? |
I'm using Spring ldap rather than pure JNDI. Let me check it your way |
Sascha Szott (Migrated from LDAP-319) said:
So far Spring LDAP does not support pagination in conjunction with
LdapRepository
(and its concrete subclasses). This makes it hard to usefindAll
in cases with more than 1000 result objects. Are there any plans to extendSimpleLdapRepository
in order to support pagination?The text was updated successfully, but these errors were encountered: