You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (Updated) (JIRA)" <ji...@apache.org> on 2012/02/15 18:08:59 UTC
[jira] [Updated] (DIRSTUDIO-777) Renaming entry fails when using
Apache Directory LDAP API
[ https://issues.apache.org/jira/browse/DIRSTUDIO-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSTUDIO-777:
---------------------------------------------
Fix Version/s: 2.0.0
2.0.0-M3
Assignee: Pierre-Arnaud Marcelot
Summary: Renaming entry fails when using Apache Directory LDAP API (was: Troube renaming entry when using Apache LDAP API)
> Renaming entry fails when using Apache Directory LDAP API
> ---------------------------------------------------------
>
> Key: DIRSTUDIO-777
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-777
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Environment: Windows 7 SP1 64-bit
> Reporter: Aleks M
> Assignee: Pierre-Arnaud Marcelot
> Fix For: 2.0.0-M3, 2.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira