Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 1.5.4
    • Fix Version/s: 2.0.0-M11
    • Component/s: core
    • Labels:
      None

      Description

      We've just removed the configuration in the server.xml for specifying the context entry (CE) for a partition. There were issues with implementing this with XBean - it was very messy too. Instead we now defer creation of the context entry until after the server is started. So the partition is created and present yet it does not have the context entry which makes it not seen even though the entry is listed in the RootDSE under the namingContexts attribute.

      It's disappointing to fire up the server and notice your namingContext is missing for a new partition you added. The first thing the user feels is that there's something wrong with the way they configured their partition.

      Rather than omit the CE, I suggest we have the partition infer a context entry based on the namingContext DN's RDN attribute. Partitions should be able to accept a CE in which case the inference process is bypassed. If omitted though the CE is inferred. Some examples:

      For o=apache:

      dn: o=apache
      objectClass: top
      objectClass: organization
      objectClass: extensibleObject
      o: apache

      For dc=apache,dc=org

      dn: dc=apache,dc=org
      objectClass: top
      objectClass: domain
      objectClass: extensibleObject
      dc: apache

        Issue Links

          Activity

          Hide
          Emmanuel Lecharny added a comment -

          I agree 100% with this approach. However, I would start with a simple injection of an entry with all the RDN AVAs and the extensibleObject objectClass (not trying to infer the ObjectClasses from the RDN...)

          Show
          Emmanuel Lecharny added a comment - I agree 100% with this approach. However, I would start with a simple injection of an entry with all the RDN AVAs and the extensibleObject objectClass (not trying to infer the ObjectClasses from the RDN...)
          Hide
          Alex Karasulu added a comment -

          Yep that will definitely work and easier to implement really quickly.

          Show
          Alex Karasulu added a comment - Yep that will definitely work and easier to implement really quickly.
          Hide
          Stefan Zoerner added a comment -

          I recommend to infer a context entry only for JDBM or XDBM partitions, not partitions in general. If a developer has created a partition on his/her own, he/she should be able to decide what should happen with the context entry.

          Show
          Stefan Zoerner added a comment - I recommend to infer a context entry only for JDBM or XDBM partitions, not partitions in general. If a developer has created a partition on his/her own, he/she should be able to decide what should happen with the context entry.
          Hide
          Alex Karasulu added a comment -

          That's a good point. I think we can make it so this is only the case in a default constructor of the base class. Another can provide the argument for the specified CE which bypasses any such inference process.

          Show
          Alex Karasulu added a comment - That's a good point. I think we can make it so this is only the case in a default constructor of the base class. Another can provide the argument for the specified CE which bypasses any such inference process.
          Hide
          Emmanuel Lecharny added a comment -

          Let's do that for 2.0

          Show
          Emmanuel Lecharny added a comment - Let's do that for 2.0
          Hide
          Emmanuel Lecharny added a comment -

          Moved back to 2.0.0-RC1

          Show
          Emmanuel Lecharny added a comment - Moved back to 2.0.0-RC1
          Hide
          Pierre-Arnaud Marcelot added a comment -

          Version 2.0.0-M1 has been released.
          Moving all related non-resolved issues to the next version.

          Show
          Pierre-Arnaud Marcelot added a comment - Version 2.0.0-M1 has been released. Moving all related non-resolved issues to the next version.
          Hide
          Pierre-Arnaud Marcelot added a comment -

          Version 2.0.0-M3 has been released a couple months ago.

          Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).

          Show
          Pierre-Arnaud Marcelot added a comment - Version 2.0.0-M3 has been released a couple months ago. Assigned the remaining opened JIRA to the next iteration (2.0.0-M4).
          Hide
          Emmanuel Lecharny added a comment -

          Fixed

          Show
          Emmanuel Lecharny added a comment - Fixed

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development