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 2010/05/26 14:26:53 UTC
[jira] Updated: (DIRSERVER-1236) Store an AttributeEntry object in
filter's node
[ https://issues.apache.org/jira/browse/DIRSERVER-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1236:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> Store an AttributeEntry object in filter's node
> -----------------------------------------------
>
> Key: DIRSERVER-1236
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1236
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.3
> Reporter: Emmanuel Lecharny
> Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> The Filter's nodes contain a String to describe the associated attribute. As the filters are parsed and normalized, it would be much better to store an AttributeEntry instead.
> The reason for this modification is that it will simplify such code :
> AttributeType at = session.getCoreSession().getDirectoryService()
> .getRegistries().getAttributeTypeRegistry().lookup( presenceNode.getAttribute() );
> if ( at.getOid().equals( SchemaConstants.OBJECT_CLASS_AT_OID ) )
> {
> which will become :
> if ( presenceNode.getAttribute().getOid().equals( SchemaConstants.OBJECT_CLASS_AT_OID ) )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.