Closed Bug 919249 Opened 12 years ago Closed 1 year ago

Rename failed with referral when move one entry

Categories

(Directory Graveyard :: LDAP Java SDK, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: hxbon1y, Unassigned)

Details

User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; SE 2.X MetaSr 1.0) Steps to reproduce: Invoke netscape.ldap.LDAPConnection.rename(String dn,String newRDN,String newParentDN,boolean deleteOldRDN) to move one entry from one ou to another ou, the two OU are all in a referred server. we use the connection which connected to a primary server which contains the referral which contains the two OUs. I debug the SDK source, it found the entry is not in primary server and will throw a LDAPReferralException, and then catch the exception to handle referral. Then it will established a temporary connection with referred server and re-invoke rename API on the temporary connection. But it only invoke one API wich can rename entry, not invoke the API which can move entry. the primary source as following: ------------ void referralOperation(LDAPConnection connection, LDAPConstraints cons, int ops, String dn, int scope, String filter, String types[], boolean attrsOnly, LDAPModification mods[], LDAPEntry entry, LDAPAttribute attr, Vector results) throws LDAPException { ...... case JDAPProtocolOp.MODIFY_RDN_REQUEST: connection.rename(dn, filter /* newRDN */, attrsOnly /* deleteOld */, cons); break; so this transparently is a bug in source. Actual results: Move entry failed. Expected results: Move entry successfully with rererral.
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.