Issue #162 has been reported by Rémy-Christophe Schermesser. ---------------------------------------- Feature #162: Migrate from JNDI to UnboundId LDAP SdK http://tools.lsc-project.org/issues/show/162
Author: Rémy-Christophe Schermesser Status: New Priority: Normal Assigned to: Category: Target version: 1.3 branch I have tested the UnboundId LDAP SDK for Java and it is very easy to use, well easier than JNDI (but what is harder to use than JNDI ? :)). And I think we should migrate from JNDI to this API. Why ? Because the undoundid sdk : * is thread safe, and with the server mode for LSC, I think it is *very* important * is easier to use, is more Java 1.5+ compliant and is actively developed (I think JNDI has not changed since Java 1.5 and it was only for adding some generics) I have looked in the LSC code, and there is a lot of public APIs that uses JNDI objects. So I have thought of two ways to make this migration : * Add deprecation warnings in the 1.2 to all the API that uses JNDI, and make the migration in 1.3 * Use the migration package of UnboundID (http://www.unboundid.com/products/ldapsdk/docs/javadoc/com/unboundid/ldap/sdk/migrate/jndi/JNDIConverter.html), and only change the interior of all our classes. The first solution is a radical one (so I like it very much :)) The second solution will add overhead to the LSC What do you think ? Do you have more idea ? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
