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

Alex Karasulu closed DIRSERVER-630.
-----------------------------------

    Fix Version/s: 1.1.0
                   1.0-RC4
       Resolution: Fixed

Committed revision 428222 to 1.0 branch.  Patch applied to 1.1 on revision 
428223.


> 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
>          Issue 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
>         Assigned To: Alex Karasulu
>             Fix For: 1.1.0, 1.0-RC4
>
>         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

        

Reply via email to