directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbert Reilly (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-630) If one tries to add an attribute without any value, an (illegal) attribute with empty value is created
Date Sun, 04 Jun 2006 05:14:30 GMT
    [ ] 

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:
>      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:
> 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,, 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:
For more information on JIRA, see:

View raw message