Bug 124342 (DEFECT000065536)

Summary: Test-- NameClassPair.getName() on names with multiple \'s does not seem t ...
Product: [Novell Products] NDS SDK Reporter: Rajkumar V <vrajkumar>
Component: JNDIAssignee: Parameswaran S <sparamesh>
Status: RESOLVED FIXED QA Contact: Sundar Swamy <ssundar>
Severity: Normal    
Priority: P5 - None CC: aclark
Version: OCT 2006 NDKKeywords: English
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

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


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

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

---------
<remedy_version_found_in> All </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> Test-- NameClassPair.getName() on names with multiple
      \'s does not seem to work.  I created two bazzare users:
   BizzareUser1       = "cn=Hoser\\\\\\\\\\\\\\\\user"
   BizzareUser2       = "cn=Hoser\\\\\\\\"
They appear like this in the nwadmin:
Hoser\\\\user
Hoser\\
But the following code can not delete them:
               while(enum.hasMoreElements())
               {
                  ncp = (NameClassPair) enum.nextElement();
                  try
                  {
                     orgToDel.destroySubcontext(ncp.getName());
                  }
                  catch(Exception dse)
                  {
                     logErr(dse, "Exeption thrown while deleting object :"
                     + ncp);
                  }
               }
If I feed the name to destroySubcontext my self they are deleted just fine.
<TAG,981014,mborup,Entered-0,TAG>
 </remedy_details>
---------
<remedy_notes> aclark (  9/14/99 4:57:20 PM  Testing - Information
      Required ) This was reported against a different service provider.
      Verify that this is still an issue with the LDAP service provider.
Files Involved:  , </remedy_notes>
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, vrajkumar@novell.com.
   Previous reporter was mborup@novell.com.