attribute resolver issues after upgrade to v3

Cantor, Scott cantor.2 at
Fri Aug 14 22:00:00 EDT 2015

FWIW, code review of V2 does not suggest that there's any whitespace trimming in the LDAP filter construction step, and no indication that an attribute whose values are all null in a database would satisfy isEmpty() in the LDAP filter template code. At least not with the 2.4 branch.

The whitespace issue could easily be a vt-ldap thing, but the second just can't be true. Nulls are added to the value collection in V2 as Java nulls, and an ArrayList containing any null objects is not empty.

It is a difference that the actual values returned from a get() are not the same (null in V2, EmptyAttributeValue instances in V3). I'll check if we documented that.

-- Scott

More information about the users mailing list