Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <6924979.1156097475463.JavaMail.jira@brutus>
Date: Sun, 20 Aug 2006 11:11:15 -0700 (PDT)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSERVER-646) Replacing an unknown attribute with
 no values (deletion) causes an error
In-Reply-To: <24345340.1150201409764.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DIRSERVER-646?page=all ]

Alex Karasulu updated DIRSERVER-646:
------------------------------------

    Priority: Critical  (was: Minor)

> Replacing an unknown attribute with no values (deletion) causes an error
> ------------------------------------------------------------------------
>
>                 Key: DIRSERVER-646
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-646
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3, 1.0-RC4
>         Environment: ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>            Reporter: Stefan Zoerner
>         Assigned To: Alex Karasulu
>            Priority: Critical
>         Attachments: ReplaceNonExistingAttribute.java
>
>
> I am not sure, whether we have implemented the following right: RFC 2251 says in chapter 4.6. (Modify Operation) the following about replace modification items:
> "replace: replace all existing values of the given attribute with the new values listed, creating the attribute if it did not already exist. A replace with no value will delete the entire attribute if it exists, and is ignored if the attribute does not exist."
> The problem I have found has to do with the second part. To make it more concrete, here is my example entry:
> dn: cn=Kate Bush,dc=example,dc=com
> cn: Kate Bush
> objectclass: top
> objectclass: person
> sn: Bush
> If I apply the following modification to it (replace with no value)
> dn: cn=Kate Bush,dc=example,dc=com
> changetype: modify
> replace: description
> -
> i.e.
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -f replaceDescription.ldif
> modifying entry cn=Kate Bush,dc=example,dc=com
> $
> ApacheDS works as expected and described in the RFC above: Nothing happens (especially no error).  
> If I use an attribute which is not known to the server, e.g.
> dn: cn=Kate Bush,dc=example,dc=com
> changetype: modify
> replace: numberOfOctaves
> -
> The following happens
> $ ldapmodify -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -f replaceOctaves.ldif
> modifying entry cn=Kate Bush,dc=example,dc=com
> ldap_modify: Undefined attribute type
> ldap_modify: additional info: failed to modify entry cn=Kate Bush,dc=example,dc=com
> $
> I am not sure, whether the correct behavior is to ignore the replace modification here. But I assume it (what does "is ignored if the attribute does not exist" exactly mean in the RFC?). Sun Java System Directory Server 5.2. for instance does not throw an error in this situation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira