the issue here is that we do a check for the ancestors in another class [1] which is used while searching but not during lookup
Kiran Ayyagari [1] http://svn.apache.org/repos/asf/directory/apacheds/trunk/core-api/src/main/java/org/apache/directory/server/core/filtering/BaseEntryFilteringCursor.java line 463 On Tue, Jul 27, 2010 at 3:47 AM, Alex Karasulu <[email protected]> wrote: > Exactly this was implemented purposefully as part of the protocol. Ask for > 'shape' and u get circles, squares and triangles. > > Sent from my iPhone > > On Jul 27, 2010, at 1:00 AM, Quanah Gibson-Mount <[email protected]> wrote: > >> --On Monday, July 26, 2010 11:57 PM +0200 Emmanuel Lecharny >> <[email protected]> wrote: >> >>> Hi guys, >>> >>> I had 3 days off, and that was good ! >>> >>> However, I didn't spent all my time seeping and looking at the sun. I >>> fixed a few problems in the Collective Attributes handling (mainly schema >>> related issues). >>> >>> We have some more issues to fix, one which is annoying is that you can do >>> a search requesting for a specific attributeType, or for a subtype, and >>> you'll get it. For instance, if your entry has a 'cn' attribute, you will >>> get it if you ask for the 'name' attributeType (you'll get every >>> attributeType subtyping 'name', like 'sn', etc, if they exist). It does >>> not work for lookup. >> >> Isn't that the way it is supposed to work? >> >> [zim...@build08 ~]$ ldapsearch -LLL -x -H ldapi:/// -D "cn=config" -W >> "(uid=testuser1)" name >> Enter LDAP Password: >> dn: uid=testuser1,ou=people,dc=build08,dc=lab,dc=zimbra,dc=com >> sn: testuser1 >> cn: testuser1 >> >> >> >> --Quanah >> >> -- >> >> Quanah Gibson-Mount >> Principal Software Engineer >> Zimbra, Inc >> -------------------- >> Zimbra :: the leader in open source messaging and collaboration >
