Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.0-M2 (2.0.0.v20120127)
-
None
-
Windows 7 SP1 64-bit
Description
Another thing that happens only with the Apache LDAP API.
If I against my eDirectory want to perform a rename on an entry with F2.
If the object is named manuell1000-setla1 and I want to rename it to manuell1000-SETLA1
I.e. I'm only changing the case the I get this error when using the Apache API:
Error while renaming entry
- [LDAP: error code 68 - NDS error: entry already exists (-606)]
java.lang.Exception: [LDAP: error code 68 - NDS error: entry already exists (-606)]
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1259)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$500(DirectoryApiConnectionWrapper.java:107)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$5.run(DirectoryApiConnectionWrapper.java:845)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1161)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1095)
at org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.renameEntry(DirectoryApiConnectionWrapper.java:867)
at org.apache.directory.studio.ldapbrowser.core.jobs.RenameEntryRunnable.renameEntry(RenameEntryRunnable.java:306)
at org.apache.directory.studio.ldapbrowser.core.jobs.RenameEntryRunnable.run(RenameEntryRunnable.java:165)
at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:109)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
[LDAP: error code 68 - NDS error: entry already exists (-606)]
If I switch to JNDI and perform the exact same operation I get no error, it renames the entry.