Le 20/05/2018 à 23:22, Stefan Seelmann a écrit :
> Hi Emmanuel,


Hi Stefan,


> 
> please review this change.
> 
> There was a failing test in Studio, it was not possible to delete a
> complex DN in member attribute because the server respondes withe "non
> existing value".
> 
> The problem was in the Value.equals() method, where an already
> normalized value was normalized a 2nd time. For complex DNs this 2nd
> normalizing fails. I added a test ModifyMemberIT to demonstrate the problem.


Your change makes totally sense : a Value is always already normalized
as soon as it has an AttributeType.

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org

Attachment: pEpkey.asc
Description: application/pgp-keys

Reply via email to