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)" <di...@incubator.apache.org> on 2005/09/10 06:10:30 UTC

[jira] Closed: (DIREVE-238) Define operational attributes within entries to point to including subentries

     [ http://issues.apache.org/jira/browse/DIREVE-238?page=all ]
     
Alex Karasulu closed DIREVE-238:
--------------------------------

    Resolution: Fixed

Done!

> Define operational attributes within entries to point to including subentries
> -----------------------------------------------------------------------------
>
>          Key: DIREVE-238
>          URL: http://issues.apache.org/jira/browse/DIREVE-238
>      Project: Directory Server
>         Type: Sub-task
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu
>      Fix For: 0.9.3

>
> Rather than enumerate through the set of subentries testing their subtreeSpecification for entry inclusion in their entry collection its best to compute inclusion and store a reference to the subentry in the entry using operational attributes.  What I'm thinking of exactly is to use operational attributes to store the DN of the subentry.  These operational attributes must be computed whenever an entry is added.  No need to worry about modifyRdn operations since this does not change the scope of the entry relative to the administration point. 
> The operational attribute interceptor must be modified to inject these attributes into the entry when they are added.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira