Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 40891 invoked from network); 8 Feb 2005 23:36:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Feb 2005 23:36:14 -0000 Received: (qmail 11683 invoked by uid 500); 8 Feb 2005 23:36:14 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 11563 invoked by uid 500); 8 Feb 2005 23:36:13 -0000 Mailing-List: contact directory-dev-help@incubator.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 directory-dev@incubator.apache.org Received: (qmail 11550 invoked by uid 99); 8 Feb 2005 23:36:13 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_MESSAGE,HTML_NONELEMENT_20_30 X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.vergenet.com (HELO mail.vergenet.com) (216.140.187.25) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 08 Feb 2005 15:36:12 -0800 Received: from endi (unknown [192.168.0.52]) by mail.vergenet.com (Postfix) with ESMTP id C353F13FE4 for ; Tue, 8 Feb 2005 17:18:13 -0600 (CST) From: "Endi Sukma Dewata" To: Subject: Problem with mixed case in suffix Date: Tue, 8 Feb 2005 17:36:05 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C50E04.AAE46500" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Thread-Index: AcUONvT3PTxSs3spSfujW9+iZa1/CA== Message-Id: <20050208231813.C353F13FE4@mail.vergenet.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C50E04.AAE46500 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, I'm Endi Dewata from Verge Archemedia Labs in Austin, TX. I'm working with Adison Wongkar trying to hook up our Virtual Directory product with ApacheDS. So far so good, but it seems that we just found a minor problem with suffixes that contain capital letters (e.g. dc=VergeNet,dc=com). It's not a blocking problem for us, but I just want to know if this is a known issue or has been addressed before. Here's the description of the problem: In ServerContextFactory.java line #630, JdbmDatabase is initialized with un-normalized suffix. Database db = new JdbmDatabase( upSuffix, wkdir ); But in JdbmDatabase.java line #673, when adding an entry to the database, the suffix is compared with the normalized dn of the new entry. if ( dn.equals( suffix ) ) This is causing the add operation to fail. A similar problem also happens here. In RootNexus.java line #203, the suffix is being normalized during registration. backends.put( backend.getSuffix( true ).toString(), backend ); However, in RootNexus.java line #556, the dn used to look up the backend is not normalized. return ( ContextPartition ) backends.get( clonedDn.toString() ); This is causing the search operation to fail. Should I file a bug? Thank you very much. -- Endi S. Dewata ------=_NextPart_000_001C_01C50E04.AAE46500 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi,

 

I’m Endi Dewata from Verge Archemedia Labs in = Austin, TX. I’m working with Adison Wongkar trying to hook up our Virtual = Directory product with ApacheDS. So far so good, but it seems that we just found a = minor problem with suffixes that contain capital letters (e.g. = dc=3DVergeNet,dc=3Dcom). It’s not a blocking problem for us, but I just want to know if this is a = known issue or has been addressed before. Here’s the description of the = problem:

 

 

In ServerContextFactory.java line #630, JdbmDatabase = is initialized with un-normalized suffix.

 

         =    Database db =3D new JdbmDatabase( upSuffix, wkdir = );

 

But in JdbmDatabase.java line #673, when adding an = entry to the database, the suffix is compared with the normalized dn of the new = entry.

 

        if ( = dn.equals( suffix ) )

 

This is causing the add operation to = fail.

 

 

A similar problem also happens here. In = RootNexus.java line #203, the suffix is being normalized during = registration.

 

        = backends.put( backend.getSuffix( true ).toString(), backend = );

 

However, in RootNexus.java line #556, the dn used to = look up the backend is not normalized.

 

         =        return ( ContextPartition ) backends.get( clonedDn.toString() = );

 

This is causing the search operation to = fail.

 

 

Should I file a bug? Thank you very = much.

 

--

Endi S. Dewata

 

------=_NextPart_000_001C_01C50E04.AAE46500--