spring-projects / spring-projects/spring-ldap
ODM: Consider derived object classes as well
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 375
- Forks
- 501
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 63
Description
Currently for mapping LDAP entries to ODM annotated classes the objectclass field on the annotation @Entry is evaluated. The mapping considers only LDAP entries having the given class explicitly set as eligible for mapping. In some cases that objectclass is not explicitly set, but rather a more specific objectclass, which derives from the required objectclass (e.g. inetOrgPerson instead of Person). Of course those entries should also be considered when doing the mapping.
Not sure how to implement that, because to consider any derived objectclasses one would probably need to retrieve the according schema (even transitively).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ODM mapping path that evaluates the @Entry objectclass value and compare it with LDAP schema inheritance. Determine how derived objectclasses should be discovered transitively, then verify that entries using a more specific class, such as inetOrgPerson instead of Person, are eligible for mapping. The issue names no files or tests, so locate the relevant mapper and add coverage for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100