Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 89550 invoked from network); 4 Mar 2009 17:54:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Mar 2009 17:54:20 -0000 Received: (qmail 99803 invoked by uid 500); 4 Mar 2009 17:54:19 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 99757 invoked by uid 500); 4 Mar 2009 17:54:19 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 99748 invoked by uid 99); 4 Mar 2009 17:54:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 09:54:19 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2009 17:54:19 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BB36A234C4A7 for ; Wed, 4 Mar 2009 09:53:58 -0800 (PST) Message-ID: <1132730569.1236189238761.JavaMail.jira@brutus> Date: Wed, 4 Mar 2009 09:53:58 -0800 (PST) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-1322) Auto inferring context entry In-Reply-To: <2096455867.1236183478773.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678811#action_12678811 ] Alex Karasulu commented on DIRSERVER-1322: ------------------------------------------ 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. > Auto inferring context entry > ---------------------------- > > Key: DIRSERVER-1322 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1322 > Project: Directory ApacheDS > Issue Type: Improvement > Components: core > Affects Versions: 1.5.4 > Reporter: Alex Karasulu > > 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 > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.