From dev-return-13728-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Oct 02 13:54:12 2006 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 65318 invoked from network); 2 Oct 2006 13:54:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Oct 2006 13:54:12 -0000 Received: (qmail 95064 invoked by uid 500); 2 Oct 2006 13:54:09 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 95004 invoked by uid 500); 2 Oct 2006 13:54:09 -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 94947 invoked by uid 99); 2 Oct 2006 13:54:09 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Oct 2006 06:54:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received: from [209.237.227.198] ([209.237.227.198:39952] helo=brutus.apache.org) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 68/CA-16499-AF911254 for ; Mon, 02 Oct 2006 06:54:02 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9575871430D for ; Mon, 2 Oct 2006 06:53:20 -0700 (PDT) Message-ID: <5954201.1159797200608.JavaMail.root@brutus> Date: Mon, 2 Oct 2006 06:53:20 -0700 (PDT) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Closed: (DIRSERVER-556) Extract out JNDI configuration setting management code into JNDI Utils MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIRSERVER-556?page=all ] Alex Karasulu closed DIRSERVER-556. ----------------------------------- fixed and confirmed > Extract out JNDI configuration setting management code into JNDI Utils > ---------------------------------------------------------------------- > > Key: DIRSERVER-556 > URL: http://issues.apache.org/jira/browse/DIRSERVER-556 > Project: Directory ApacheDS > Issue Type: Sub-task > Reporter: Alex Karasulu > Assigned To: Trustin Lee > > The property handling logic in the JNDI code can get out of control very rapidly. Some of the logic is a direct reflection of JNDI LDAP provider guidelines and can be reused. However more importantly we need to get this stuff out of the way so it does not clutter things up. So we need some JNDI LDAP provider utilities for centralizing code dealing with environment settings. -- 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