Bug 124380 (DEFECT000310998)

Summary: LDAPObjectClassSchema.setQualifier() not working or sample wrong
Product: [Novell Products] NDS SDK Reporter: Susan Perrin <susan.perrin>
Component: LDAP Java SDKAssignee: Parameswaran S <sparamesh>
Status: VERIFIED FIXED QA Contact: Sundar Swamy <ssundar>
Severity: Minor    
Priority: P5 - None CC: aclark
Version: OCT 2006 NDKKeywords: Code_Error, English
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: ExtendSchema.java

Description Rajkumar V 2005-10-10 22:54:47 UTC 


------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000310998 at remedy/
remedy/show_bug.cgi?id=DEFECT000310998
Originally filed under the NDS SDK product and LDAP Java SDK component.

---------
<remedy_version_found_in> Sept NDK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> I use ExtendSchema.java to create a class.  Note the
      following lines in ExtendSchema.java:

        // Add Novell eDirectory specific flags for object class definition
        newObjClass.setQualifier( "X-NDS_NAMING", new String [] {"cn"});
        newObjClass.setQualifier( "X-NDS_CONTAINMENT", new String []
            {"organization", "organizationalUnit", "domain", "locality",
                                                                  "treeRoot"});

However, after I create the object, the X-NDS properties aren't set.  Here is
my schema definition that I get when I run this sample:

objectClasses: ( 2.16.840.1.113719.1.186.6.1 NAME 'testClass' DESC 'Test class
  definition' SUP top STRUCTURAL MUST ( cn $ title ) X-NDS_NAMING ( 'cn' 'titl
 e' ) X-NDS_CONTAINMENT ( 'organization' 'organizationalUnit' 'country' 'local
 ity' 'domain' ) X-NDS_NAME 'testClass' )

Notice that x-nds_naming is set to BOTH cn and title, even though it should
ONLY be set to cn.

My ldap trace of the create is below, and it doesn't show the x-nds flags
being sent as part of the schema modify for the objectclass:


LDAP:   [08/20/2002 11:07:52.66]: (0x0416e380:0x0005:0x66) Incoming Decode
0000  02 01 05 66 81 9E 04 09 63 6E 3D 73 63 68 65 6D ...f....cn=schem
0010  61 30 81 90 30 81 8D 0A 01 00 30 81 87 04 0D 6F a0..0.....0....o
0020  62 6A 65 63 74 43 6C 61 73 73 65 73 31 76 04 74 bjectClasses1v.t
0030  28 20 32 2E 31 36 2E 38 34 30 2E 31 2E 31 31 33 (.2.16.840.1.113
0040  37 31 39 2E 31 2E 31 38 36 2E 36 2E 31 20 4E 41 719.1.186.6.1.NA
0050  4D 45 20 27 74 65 73 74 43 6C 61 73 73 27 20 44 ME.'testClass'.D
0060  45 53 43 20 27 54 65 73 74 20 63 6C 61 73 73 20 ESC.'Test.class.
0070  64 65 66 69 6E 69 74 69 6F 6E 27 20 53 55 50 20 definition'.SUP.
0080  74 6F 70 20 53 54 52 55 43 54 55 52 41 4C 20 4D top.STRUCTURAL.M
0090  55 53 54 20 28 20 63 6E 20 24 20 74 69 74 6C 65 UST.(.cn.$.title
00A0  20 29 20 29                                     .).)

LDAP:   [08/20/2002 11:07:52.66]: (0x0416e380:0x0005:0x66) DoModify on
connection 0x416e380
LDAP:   [08/20/2002 11:07:52.66]: (0x0416e380:0x0005:0x66) modify: dn
(cn=schema)

Is the sample wrong, or is setQualifier broken? </remedy_details>