You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/03/20 00:19:32 UTC
[jira] Created: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
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
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.
[jira] Commented: (DIRSERVER-874) Entries should be normalized in
the NormalizationService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626787#action_12626787 ]
Emmanuel Lecharny commented on DIRSERVER-874:
---------------------------------------------
Now that we are removing JNDI from the frontend, this issues sounds like fixed, or will be fixed soon.
Gimme a couple of more days to double check it.
> 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.5
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.1)
1.5.2
> 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.2
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-874:
----------------------------------------
Fix Version/s: 1.5.1
> 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.1
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-874:
----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> 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: 2.0.0-RC1
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.4)
1.5.5
Might need some status on this. Or are we cnvinced we want to do it. Delaying to figure this out.
> 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.5
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-874:
----------------------------------------
Fix Version/s: (was: 1.5.2)
1.5.3
Postponed.
> 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.3
>
>
> 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.
[jira] Updated: (DIRSERVER-874) Entries should be normalized in the
NormalizationService
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSERVER-874) Entries should be normalized in
the NormalizationService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482464 ]
Emmanuel Lecharny commented on DIRSERVER-874:
---------------------------------------------
Here is a summary of a convo we just have had with Alex :
We don't need to modify the server completly, but we should at least do the following :
1) Adding a new member in the RequestImpl object : a normalizedAttributes
2) Modify the AddHandler to pass this Request object to the ServerContext, instead of a DN and Attributes
3) Modify the ServerContext.createSubContext() to accept this AddRequest object
4) Adding an add operation into the Interceptor interface so that it accepts athe AddRequest object as a parameter
5) normalizing the attributes in the NormalizationService
It should help to fix the bug :)
> 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
>
> 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.