2014-12-15 12:25 GMT+01:00 Marian Harbach <[email protected]>: > > Hi Clement, > > I finally came around to look at this again. The issue seems to be that > the mainIdentifier javascript is applied twice during modification checking > in the BeanComparator. This patch fixes the problem for me: > > Index: BeanComparator.java > =================================================================== > --- BeanComparator.java (revision 2025) > +++ BeanComparator.java (working copy) > @@ -158,7 +158,7 @@ > IBean itmBean = cloneSrcBean(task, srcBean, dstBean); > > > // get modification type to perform > - LscModificationType modificationType = calculateModificationType(task, > itmBean, dstBean); > + LscModificationType modificationType = calculateModificationType(task, > srcBean, dstBean); > > > // if there's nothing to do, just return > if (modificationType == null) { > > calculateModificationType() clones the srcBean parameter again and in the > current version the already-cloned itmBean is passed in. Thus, in > calculateModifications, the DN is modified twice and fails the equals > check, causing the modrdn modification type. Can somebody verify this? > > >
Could you send us a minimal configuration that reproduces the problem? Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
