Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of elecharny@gmail.com designates
 64.233.182.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding;
        b=tzIR3UKds6Z7kDOXvqfGyBRShvYN6ay/wZvmlCRbhPemebujdOfl0v0/LkhxmwKtDudO4A8KUEQ/FPJtGvYjshnQSF1TJ4oK67mfrQV0MNSQzwiAA1vmc3KS6CTXyInUDH1byhHPwGN++S4bVi+qGWx2RMp2psJZaNJi/6FvaIQ=
Subject: Oids global access
From: Emmanuel Lecharny <elecharny@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
In-Reply-To: <452648305.1133998571050.JavaMail.jira@ajax.apache.org>
References: <452648305.1133998571050.JavaMail.jira@ajax.apache.org>
Content-Type: text/plain
Date: Thu, 08 Dec 2005 02:17:46 +0100
Message-Id: <1134004666.7846.136.camel@portable>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi all,

I have a problem : I want to be able to access the Name <-> Oid Map, to
be able to transform names to oid when parsing a DN (this is related to
DIRLDAP-73 bug : http://issues.apache.org/jira/browse/DIRLDAP-73 )

What I want to do is simple : translating any DN to its counterpart
using oid instead of names, like :

ou=People, dc=example, dc=com

will be transformed to : 

2.5.4.11=People, 0.9.2342.19200300.100.1.25=example,
0.9.2342.19200300.100.1.25=com

(I'm talking of the internal representation of the DN, not the User
Provided DN, which will remain the same)

To do that, I need to read the HashMap where is stored all the Name/Oid
maps. It's currentrly stored in the oidRegistry.

The problem is that this Map is not accessible directly. 

I think that the best place to do the translation is in DnParser, thus I
need a static oidRegistry I can read from the parser.

This is not something complicated to do, but I'm just asking myself : is
there any better solution ?

(Of course, rethinking the way DN are parsed/normalized is possible, but
not for 1.0)

I welcome any suggestion !

--Emmanuel