Issue #445 has been updated by Clément OUDOT.
Sébastien Bahloul wrote: > Thanks for this patch Raphaël. Before commiting it, is there a way to > retrieve the event of entry deletion ? If so, I think that it could be cool > to modify the event based synchronization process to support it. Raphaël posted a mail about this: > I'm working on some issues with synchronous synchronization based on SyncRepl. > > I wanted to know what is the desired behavior. I see essentially two > scenarios: > A. All is handled with sync protocol > A.1: automatic complete sync phase (works fine) > A.2: automatic complete clean phase (not implemented) > A.3: handle SyncRepl event: > A.3a: handle add (OK) > A.3b: handle modify (not tested, but should be OK) > A.3c: handle delete (not implemented) > A.3d: handle present (?) > > A.3 can be different depending on the LDAP server. e.g. for SUN/Novell/OpenDJ > there would be no present but there would be a modrdn. For Active Directory I > don't know which entries are sent by the server. > > B. Handle only add/modify > B.1: automatic complete sync phase (works fine) > B.2: handle incoming entries (works fine but deleted entries, see #445) > > In this case we must support deleting separately, by allowing to launch LSC > with -c option for a asyncLdapSourceService (see #35). > > LSC code seems to be nearer of B, I can work to fix the last issues. But I > would like to be sure it is the desired behavior. So Sébastien, what is your prefered behavior, A or B? ---------------------------------------- Bug #445: Error (NPE) when deleting an entry in the source directory with asyncLdapSourceService http://tools.lsc-project.org/issues/445 Author: Clément OUDOT Status: New Priority: Normal Assigned to: Category: Core Target version: 2.0 Problem in version: 2.0rc2 When launching LSC with asyncLdapSourceService, when a delete is done in the source repositry, we get an error in LSC: <pre> avr. 20 14:56:00 - ERROR - Error while synchronizing ID {}: java.lang.NullPointerException </pre> Indeed, when trying to reproduce this behvior with ldapsearch using syncrepl control, we see that a delete send the dn in the persistent search: <pre> clement@ader:~/Programmes/openldap$ bin/ldapsearch -H ldap://localhost:3389 -D ou=lsc,ou=accounts,ou=XXX -w secret -b ou=people,ou=XXX '(objectClass=person)' -E sync=rp -vvv dn: uid=charles.patr4,ou=people,ou=XXX control: 1.3.6.1.4.1.4203.1.9.1.2 false MEsKAQMEEOgfw2ofMxAxlEYhXTyFLmwENHJpZD 0wMDAsY3NuPTIwMTIwNDIwMTI1NTU5LjEzNzI4N1ojMDAwMDAwIzAwMCMwMDAwMDA= </pre> -- 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
