Le 18 avril 2012 10:38, Sébastien Bahloul <[email protected]> a écrit : > Hi Clement, > >> >> Are you sur this sill not erase values in destination if they changed? >> The goal is to create the objectClass attribute with some values, and >> then never modify it (it can be modified in the destination). > > > So in your case, you should not retrieve any objectClass attribute from the > source and use createValues for the objectClass on the destination.
Yes, if you look at my first mail, this is what is in my configuration. >> >> The other problem for me, is that my configuration works perfectly >> with a ldapSourceService but not with asynLdapSourceService. >> > Ok, so the exact issue is that the asyncLdapSourceService retrieves all the > attributes without taking into account the parameters specified ? Yes, there is a first issue here: fetchedAttributes are ignored in asyncLdapSourceService. Maybe there is another issue, because, even if I have the objectClass attribute in my source bean, with a dataset configuration on objectClass, the source objectClass values should be ignored and only values from the dataset <createValues/> should be push to the destination, no? Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
