[
https://issues.apache.org/jira/browse/DIRSERVER-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683514#comment-13683514
]
Konrad Windszus commented on DIRSERVER-1859:
--------------------------------------------
Why do we have that limitation? Even by deleting only I can seriously damage
things. So updating a schema is no worse than deleting schemas in my regard.
Why don't you allow updating existing ones? Is there any technical reason for
that?
I have the use case of trying out several different schemas. By just importing
one LDIF I want to return to that defined snapshot of schemas. I don't care
whether they currently exist in the system. That is the whole point about
having the "Update existing items" checkbox in the dialog.
> Importing an LDIF with a schema twice leads to "LDAP: error code 53 -
> UNWILLING_TO_PERFORM" although "Update existing items" was checked
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1859
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1859
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M12
> Reporter: Konrad Windszus
> Attachments: demo-schema.ldif
>
>
> Issue was originally created in DIRSTUDIO-914 but it turned out to be a
> problem with the LDAP server itself:
> ====
> Import the attached LDIF twice and for the second import select "Update
> existing items". The second import fails with this exception
> {code}
> Error while importing LDIF
> - [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType :
> MODIFY_REQUES
> java.lang.Exception: [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for
> MessageType : MODIFY_REQUEST
> Message ID : 46
> Modify Request
> Object : 'ou=syntaxCheckers,cn=demo,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> objectclass: top
> objectclass: organizationalUnit
> Modification[1]
> Operation : replace
> Modification
> ou: syntaxcheckers
> org.apache.directory.api.ldap.model.message.ModifyRequestImpl@f7eff827: null]
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1279)
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$600(DirectoryApiConnectionWrapper.java:109)
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$4.run(DirectoryApiConnectionWrapper.java:725)
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1174)
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1108)
> at
> org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.modifyEntry(DirectoryApiConnectionWrapper.java:747)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:474)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.run(ImportLdifRunnable.java:218)
> 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 53 - UNWILLING_TO_PERFORM: failed for MessageType :
> MODIFY_REQUEST
> Message ID : 46
> Modify Request
> Object : 'ou=syntaxCheckers,cn=demo,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> objectclass: top
> objectclass: organizationalUnit
> Modification[1]
> Operation : replace
> Modification
> ou: syntaxcheckers
> org.apache.directory.api.ldap.model.message.ModifyRequestImpl@f7eff827: null]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
