Bug 124351 (DEFECT000277741)

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

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

---------
<remedy_version_found_in> Sept NDK </remedy_version_found_in>
---------
<remedy_details> Like it or not, the Netscape LDAP SDK is the one
      others are measured against. On the Netscape SDK, when you call the
      toString() method of LDAPEntry, LDAPAttribute, LDAPModification, etc,
      it returns a descriptive string that represents the entry, attribute,
      or modification pretty well.

If you call toString() on those classes in the Novell LDAP Libraries for Java,
you get a meaningless object identifier as the string.

I used to use the strings Netscape would return as part of the trace messages
for my driver in DSTrace. Since I switched to Novell's SDK I've had to
extract the information that I want to print from those classes myself. It
doesn't take a lot more work, but I think it would be nice if toString()
returned something more representative of the object. </remedy_details>
---------
<remedy_notes> vtag (  8/6/2002 10:53:09 AM  Fixing - Approved
      for Investigation ) Tostring methods added to LDAPAttribute,
      LDAPAttributeSet, LDAPEntry modeled after the format used by the
      Netscape API.

vtag (  7/31/2002 1:57:38 PM  Fixing - New ) Steve Trottier sent toString
code for LDAPAttribute.  See if he has others, and evaluate what toString
means for the various objects.

 </remedy_notes>