Emmanuel,

On 3/5/07, Emmanuel Lecharny <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:[vbco
l=seagreen]
>
> Alex Karasulu a écrit :
> 
>
> I don't really know when this problem appeared first.[/vbcol]


Yeah I don't know either when the problem occurred but Stefan had
noticed the problem after releasing 1.0.1.

What we can do is
> to provide the user with the standard attribute value (ie objectClass,
> not ObjectClass), but we will have to browse the code for all the places
> where we compare an attribute type against a String without taking care
> of case sensitivity. A new method have been added in AttributeUtils to
> do that one month ago.


Oh really? Let's use it then.

I won't favor the case where the user search for, say, (OBJECTCLASS=*)
> and excpect to receive :
> dn: dc=example,dc=com
> dc: example
> OBJECTCLASS: domain
> OBJECTCLASS: extensibleObject
> OBJECTCLASS: top


Hmmm ok will this be to hard to accomplish?  Is this all happening because
Rdn
class normalizes by default the attribute id?

Alex

 
> https://issues.apache.org/jira/brow...action_12477613
> ] 
> -b 
> entries, 
>
>

[ Post a follow-up to this message ]