I'm a new user of Spring LDAP 1.1 (thanks btw!). And my LDAP server is E-directory. I'm using the example in the spring-ldap-reference docs as a template for my code.
When I call create(Person) everything is fine. When i call update(Person) and set objectclass in mapToContext() I will trigger a change identification for objectclass in getModificationItems() later because E-directory adds it's own objectclasses: Top and ndsLoginProperties.
When i call modifyAttributes() I get a schema violation because I'm trying to remove objectclasses that should not be removed.
I'm currently marking my Person object as persisted in storage to avoid setting objectclass attributevalues on already persisted items but I'm wondering what you think of my problem and any ideas on how to solve it in a different more general maner.