[
https://issues.apache.org/jira/browse/DIRSERVER-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-832:
----------------------------------------
Fix Version/s: (was: 1.5.1)
1.5.2
Postponed to 1.5.2, as we will have to seriously modify the way we address the
schema. I have started adding TODO Fix DIRSERVER-832 in the code each time
there is a potential pb related to this issue.
> 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
> Assignee: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.5.2
>
>
> 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.
