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: <23232289.1156198275953.JavaMail.jira@brutus>
Date: Mon, 21 Aug 2006 15:11:15 -0700 (PDT)
From: "Ersin Er (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Assigned: (DIRSERVER-709) Special case, in which removal of
 objectClass attribute does not cause an error
In-Reply-To: <206765.1155984013930.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-709?page=all ]

Ersin Er reassigned DIRSERVER-709:
----------------------------------

    Assignee: Ersin Er  (was: Alex Karasulu)

> Special case, in which removal of objectClass attribute does not cause an error
> -------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-709
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-709
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC4
>         Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
>            Reporter: Stefan Zoerner
>         Assigned To: Ersin Er
>            Priority: Minor
>         Attachments: DeleteObjectClassAttributeJndiTest.java, DeleteObjectClassAttributeNetscapeTest.java
>
>
> In a special case, removal of the objectClass attribute in a certain way does not cause an error (no exception occurs). The entry is unchanged (which is correct), thus this is only a minor problem from my point of view. Here it is:
> If one creates an entry like this:
> dn: cn=Kate Bush,dc=example,dc=com
> objectclass: top
> objectclass: person
> objectclass: organizationalperson
> objectclass: inetorgperson
> sn: Bush
> cn: Kate Bush
> and performs the following modify operation with JNDI
> ModificationItem delModOp = new ModificationItem(DirContext.REMOVE_ATTRIBUTE, new BasicAttribute("objectclass", ""));
> ctx.modifyAttributes("cn=Kate Bush", new ModificationItem[] { delModOp });
> the method call of modifyAttributes does not throw an exception. The expected retuirn code is 69 (OBJECT_CLASS_MODS_PROHIBITED). Note that the correct return code is provided by the server, if I perform this Java code:
> ModificationItem delModOp = new ModificationItem(DirContext.REMOVE_ATTRIBUTE, new BasicAttribute("objectclass"));
> ctx.modifyAttributes("cn=Kate Bush", new ModificationItem[] { delModOp });
> or if the entry looks like this:
> dn: cn=Kate Bush,dc=example,dc=com
> objectclass: top
> objectclass: person
> sn: Bush
> cn: Kate Bush
> I was able to create JUnit test cases both with JNDI and Nescape SDK for Java and will attach both of them later.

-- 
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