Directory ApacheDS
  1. Directory ApacheDS
  2. DIRSERVER-402 Add Support for LDAP Subentries
  3. DIRSERVER-407

Define operational attributes within entries to point to including subentries

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Error rendering 'com.atlassian.jirafisheyeplugin:fisheye-issuepanel'. Please contact your JIRA administrators.

        Alex Karasulu made changes -
        Fix Version/s 0.9.3 [ 12310193 ]
        Project Directory Server [ 10516 ] Directory ApacheDS [ 12310260 ]
        Key DIREVE-238 DIRSERVER-407
        Alex Karasulu made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        Alex Karasulu added a comment -

        Done!

        Show
        Alex Karasulu added a comment - Done!
        Alex Karasulu made changes -
        Field Original Value New Value
        Description 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. 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.
        Alex Karasulu created issue -

          People

          • Assignee:
            Alex Karasulu
            Reporter:
            Alex Karasulu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development