Hi Emmanuel, 1++
This was definitely a pain in some of my code that needed to deal with both JNDI Names and LdapDN's but couldn't deal with them interchangeably, as in the LdapDN case the toString() result was, as you say, pretty useless from most purposes. As it happens Pierre-Arnaud and I exchanged an email about whether this behaviour was still the case inf 1.5.4 a few weeks back. I have some really dim-distant memory of discussing this with you a long time ago too - am I mistaken, or did you start a round of tidying this up once before? Thanks! On Thu, Oct 2, 2008 at 11:32 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Hi guys, > > I'm realizing that the LdapDN.toString() method returning a normalized DN > was a truly bad idea. It's used all over the code, for instance to generate > error messages, and this is obfuscating them. > > It would be way better if the toString() method returns the user provided DN > so that the semantic of this method is kept. All in all, the toString() > method is supposed to return something whichj is readable by human beings, > when 1.3.6.1.4.1.18060.0.4.0.2.1=test is not :) > > So what about replacing the current implementation to return the UP name > instead of the Normname ? > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
