Jonathan Clarke a ?crit :
> Cl?ment OUDOT wrote:
>>> Do I just have to replace it in interldap.properties, or is there other
>>> things to do (like editing the bean)? Maybe you can give me an example?
>>>
>>
>> Hello, I update my dependencies to use lsc-1.0-rc6 and try the
>> FullDNJndiService, but I see the "{0}" is interldap.properties is now
>> the
>> full DN, so the "filterId" parameters are false. How to correct it?
>>
> That is correct. The FullDNJndiService is for the case when you can
> handle all your entries by their full DN, that you know in advance. As
> it seems that this is not your case, I think maybe FullDNJndiService
> is not the solution to your problem.
>
> If I recall correctly, you want to recursively delete subentries under
> a user's entry. This is currently not supported, but maybe this should
> be considered a bug. Could you give us some more details, in
> particular, does your synchonization recognize all these subentries
> (they appear in a seach with the filterAll property)?
>
No they don't, because subentries are not the same objectClasses.
> I think that if all entries in a list are not at the same depth in the
> LDAP tree, we could delete from the bottom up, by ordering the list by
> longest DN first. Would this suit you?
I think the correct solution is to catch the LDAP error 66, and to enter
to a "deleterecursive" function. We can imagine to have a config
parameter that allows LSC to do recusrsive delete.
Cl?ment.
