Issue #466 has been updated by Sébastien Bahloul. Status changed from Assigned to Feedback % Done changed from 0 to 90
Commited in r1716 ---------------------------------------- Bug #466: Use of HashMap in get org.lsc.jndi.JndiServices.getAttrsList(String, String, int, List<String>) http://tools.lsc-project.org/issues/466 Author: Hugh Kelley Status: Feedback Priority: Normal Assigned to: Sébastien Bahloul Category: Core Target version: 2.0 Problem in version: The use of a java.util.HashMap rather than a java.util.LinkedHashMap causes LSC to lose the original order of the LDAP entries (returned by the source directory). When dealing with hierarchical relations, e.g. OUs, this leads to a number of errors and incomplete syncs. By using the LinkedHashMap, subsequent iterations are performed in the "natural" order. I have made this change in my local source and haven't noticed any detrimental side effects. -- 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
