You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2008/06/19 04:31:45 UTC

[jira] Updated: (DIRSERVER-874) Entries should be normalized in the NormalizationService

     [ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-874:
------------------------------------

    Fix Version/s:     (was: 1.5.3)
                   1.5.4

> Entries should be normalized in the NormalizationService
> --------------------------------------------------------
>
>                 Key: DIRSERVER-874
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-874
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>             Fix For: 1.5.4
>
>
> ATM, we normalize entries (ie, attributes and values) far into the server, in different places. This lead to complicated code, and duplication of operations. We can be sure that we have bugs or at least, bugs will appears as soon as more users will try to store elements which are not exactly what we expected them to be.
> The Normalization Service should normalize the attributes, as it does for the DN, to avoid such problems. Attributes normalization consist of :
> - replacing the attributeType by its OID
> - applying the normalizer on each values
> - removing duplicated values in an entry (for instance, it is possible to store two phone number, like 012345 and 01-23-45 are the same number)
> We should also normalize add, remove and modify operations in the same way, normalizing ModifcationItems
> These modifications are not exactly simple nor fast to implement, but it's mandatory and will help implementing new features in the near future.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.