Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 62330 invoked from network); 4 Jun 2006 05:15:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jun 2006 05:15:28 -0000 Received: (qmail 91006 invoked by uid 500); 4 Jun 2006 05:15:28 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 90961 invoked by uid 500); 4 Jun 2006 05:15:27 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 90950 invoked by uid 99); 4 Jun 2006 05:15:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jun 2006 22:15:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jun 2006 22:15:26 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 26A0C7141F2 for ; Sun, 4 Jun 2006 05:14:30 +0000 (GMT) Message-ID: <2572373.1149398070155.JavaMail.jira@brutus> Date: Sun, 4 Jun 2006 05:14:30 +0000 (GMT+00:00) From: "Norbert Reilly (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-630) If one tries to add an attribute without any value, an (illegal) attribute with empty value is created In-Reply-To: <18180680.1149236249815.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIRSERVER-630?page=comments#action_12414622 ] Norbert Reilly commented on DIRSERVER-630: ------------------------------------------ I've also noted, that if a custom partition passes back an attribute in this state with an Attributes result (from lookup()) or a SearchResult in the NamingEnumeration returned from a search() then the LDAP codec silently completes, but leaves the client application hung waiting for a reply. Hence the handling of valueless attributes seem to effect both a) the client and b) the response part of the LDAP codec. I'm not sure if the other codecs have problems with valueless attributes in lookup/search results too. > If one tries to add an attribute without any value, an (illegal) attribute with empty value is created > ------------------------------------------------------------------------------------------------------ > > Key: DIRSERVER-630 > URL: http://issues.apache.org/jira/browse/DIRSERVER-630 > Project: Directory ApacheDS > Type: Bug > Environment: Sun ONE Directory SDK for Java 4.1 > 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 > Attachments: IllegalModificationTest.java > > If one tries to add an attribute to an entry, and does not provide a value, it is assumed that the server does not modify the entry. We have a situation here using Sun ONE Directory SDK for Java (or Netscape, now Mozilla SDK, http://www.mozilla.org/directory/), where adding a description attribute without value to a person entry like this > dn: cn=Kate Bush,dc=example,dc=com > objectclass: person > objectclass: top > sn: Bush > cn: Kate Bush > does not fail (modify call does not result in an exception). Instead, a description attribute is created within the entry. At least the new attribute is readable with Netscape SDK (it is not visible to most UIs, because it is invalid ...). > Attached you find a test case which demonstrates the problem. It passes with Sun Java System Directory Server 5.2, for instance. Unfortunately, I was not able to create this situation with JNDI, because its LDAP Provider does not allow this (illegal) operation -- it throws an exception on the client side and does not seem to call the server at all. -- 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