Bugzilla – Bug 124387
Netvision does not believe the answer from Dev Services is correct: Brian please review
Last modified: 2006-04-19 17:48:55 UTC
------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 ------- This bug previously known as bug DEFECT000313023 at remedy/ remedy/show_bug.cgi?id=DEFECT000313023 Originally filed under the NDS SDK product and LDAP C SDK component. --------- <remedy_version_found_in> BLANK </remedy_version_found_in> --------- <remedy_milestone> BLANK </remedy_milestone> --------- <remedy_details> Open LDAP Issue Top of Form Bottom of Form Details for Incident #: 2779837 Contact: Dale Cave Company: Beta Test: eDirectory 8.7 Falcon Current Status: Resolved Date Created: 06/27/2002 Date Responded: 06/28/2002 Date Resolved: 07/17/2002 Support Center: ASC Origin: Electronic Incident Problem Type: Documentation On-Site Phone: Primary Technician: Joe Deveraux Severity: Low Description: System: LDAP Events in eDir 8.7 Problem: EVT_CREATE_ENTRY returns empty string, which is invalid, for the class name of the object Tested: inetOrgPerson, groupOfNames, organizationalUnit Notes: EVT_DELETE_ENTRY returns the class name accurately Incident History Update / Reopen <javascript:%20document.IncidentForm.submit()> Date Created Action Comment 07/17/2002 Verified Resolution Thanks Susan. 07/16/2002 Novell Sent E-mail email to dcave@netvision.com Hi Dale, The issue you report is true both of ldap event services and ndap_event services. It is an architectural design change that occured in eDirectory 8.5 and higher. I have entered a documentation error, which should be modified to specify that the objectclass will not be available on create entry events. DSE_CREATE_ENTRY (EVT_CREATE_ENTRY ) is a preevent which is thrown with as much information can be gathered prior to actually computing things like naming and the base class. DSE_CREATE_ENTRY must be triggered before the individual attribute creates are thrown, we don't want to slow down the add an further by attempting to preprocess the entry to compute the baseclass. The baseclass is not known at the time of the object create, only the list of parent objectclasses is known. To compute the immediate base class slows down object creation, and so the engineers avoid doing this. Your application can do a separate ldap read to get the operational baseclass attribute after the object has been created. I hope this helps. Thank you Susan Perrin Novell Developer Support >>>>>> System: LDAP Events in eDir 8.7 Problem: EVT_CREATE_ENTRY returns empty string, which is invalid, for the class name of the object Tested: inetOrgPerson, groupOfNames, organizationalUnit Notes: EVT_DELETE_ENTRY returns the class name accurately 07/11/2002 Active We are in the process of setting this up for the developer to dial in and take a look at it. 06/28/2002 Active Dale, My name is Joe Deveraux and I have been assigned to help you with your beta testing. It sounds like you are using persistant search? Is there anyway you could send a piece of code to test here? Thanks </remedy_details> --------- <remedy_notes> bgbrown ( 9/17/02 9:45:04 AM Fixing - Fix Is Checked-In ) The answer from developer support is correct and that situation will not be fixed. However, I was able to fix the problem by querying the entry for the base class when encoding the event data. </remedy_notes>