[
https://issues.apache.org/jira/browse/DIRSTUDIO-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766556#action_12766556
]
Martin Alderson commented on DIRSTUDIO-513:
-------------------------------------------
Stefan: On the mailing list you convinced me it was an eDirectory problem by
quoting RFC4511, section 4.6:
------------------------------------------------------------------------
........ as a single atomic operation. While individual
modifications may violate certain aspects of the directory schema
(such as the object class definition and Directory Information Tree
(DIT) content rule), the resulting entry after the entire list of
modifications is performed MUST conform to the requirements of the
directory model and controlling schema [RFC4512].
------------------------------------------------------------------------
To me, this sounds like the order of add and delete operations shouldn't matter
as far as schema validation goes. I guess you are right about the delete
operation though - it wouldn't know which value to delete. That could lead to
the object class you add being deleted immediately!
The solution you've implemented for studio sounds good, thanks.
> Do delete before add when modifying attribute values
> ----------------------------------------------------
>
> Key: DIRSTUDIO-513
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-513
> Project: Directory Studio
> Issue Type: Improvement
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0
> Reporter: Martin Alderson
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.5.0
>
>
> When connecting to Novell eDirectory and modifying the schema an "Attribute
> Or Value Exists" error occurs. This is due to the modification performing an
> add before the delete and eDirectory (wrongly) complains that the same OID
> has been used more than once before realising that the old value should be
> deleted. Note that this is a problem with eDirectory but it would be useful
> if Studio asked for the delete to be performed before the add when modifying
> an attribute value which eDirectory is OK with.
> An example of the LDIF in the modifications logs view for an operation that
> fails is:
> dn: cn=schema
> changetype: modify
> add: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [...new
> value...]
> -
> delete: objectClasses
> objectClasses: ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' [...old
> value...]
> -
> It also seems that modifying the schema on ApacheDS has the same issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
