> On Apr 3, 2015, at 6:13 PM, Emmanuel Lécharny <[email protected]> wrote: > > I would also add that wrapping JNDI is a mistake. JNDI is antiquated, > unadapted, and semantically far from LDAP. > > To be frank, I also dislike the claim that Spring-LDAP support > client-side transaction management, because it's blatanlty false. There > is nothing like a client-side transaction in the LDAP world, there is no > way you can guarantee ACID transaction on the client. I already had this > discussion back in 2006, but it seems anchored deeply on those who > designed the API, up to the point they don't accept the idea they are > misleading users using inadapted terminology.
+1 on the notion of a JNDI wrapper being suboptimal. But I do like the notion of a higher abstraction for LDAP DAO’s. For me the spring ldap api is fine, it just wraps the wrong API! To me the solution is obvious: We need a spring ldap api that wraps the apache ldap api (not jndi) my 2 cents Shawn [email protected]
