The object will maintain a Distinguished Name (DN) value as well. For LDAP, DNs are composed of tuples as well, but, they are in reverse order from FQNs, they start at the leaf of a hierarchy and proceed towards the root. Also, they use the name of the naming attribute in place of the CLASS (as in the FQN). However, we make things a bit easier on ourselves by provide unique naming attributes for every class so that, on the basis of the naming attribute, we can determine the type of class to instantiate when we pull an object from the directory.
For example, if we have an object with the following FQN: NF:nodes/MF:ab/MF:67/MF:b3 The corresponding DN is: mfid=b3,mfid=67,mfid=ab,nfid=nodes
When the object associated with this DN is read from the directory, we simply grab the first name attribute value and see what class it's associated with and instantiate that Dark Matter Wrapper object
|
|
|
|