| Alex Karasulu (JIRA) 2007-02-23, 7:11 pm |
|
[ https://issues.apache.org/jira/brow...action_12475442 ]
Alex Karasulu commented on DIRSERVER-832:
-----------------------------------------
This bug is still present. The bug is not present in 1.0.1 but in 1.5.0 and should be fixed immediately because it's just annoying. Here's a link to the test case that was added confirming the presence of the bug:
http://svn.apache.org/viewvc?view=rev&revision=511059
> Added Attributes are all case sensitive
> ---------------------------------------
>
> Key: DIRSERVER-832
> URL: https://issues.apache.org/jira/browse/DIRSERVER-832
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0, 1.0
> Reporter: Emmanuel Lecharny
> Assigned To: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.0
>
>
> The server is working, but this is pure luck !
> When we add some attribute, like ObjectClass, the values are added into it caseSensitive.
> For instance, adding 'person' and 'PERSON' is just adding two values into the attribute.
> So far, so good. Now, we have many places in the server where wo do case sensitive comparizon on suposely case insensitive values (like for objectclasses). For instance, in SchemService :
> ...
> private int getSubentryTypes( Attributes subentry ) throws NamingException
> {
> int types = 0;
>
> Attribute oc = subentry.get( "objectClass" );
>
> if ( oc.contains( "accessControlSubentry" ) ) <<<--------------- This is DAMN WRONG !!!
> ...
> At this point, I suspect the 1.0.0 version is not amendable. We must fix it in 1.5, using the MatchingRules to manage comparizons on attributes.
> I hope I'm totally wrong, but I'm really scared... It looks like you go to the doctor wor that little red spot on your skin, and it turns out you have a hopeless cancer ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|