Issue Details (XML | Word | Printable)

Key: DIRSERVER-318
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alex Karasulu
Reporter: Stefan Zoerner
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Directory ApacheDS

Adding an already existing attribute value with a modify operation does not cause an error.

Created: 01/Sep/05 06:57 AM   Updated: 10/Feb/06 12:34 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments:
  Size
Java Source File Licensed for inclusion in ASF works ModifyAddTest.java 2005-09-01 07:03 AM Stefan Zoerner 7 kB

Resolution Date: 13/Sep/05 12:41 AM


 Description  « Hide
If you try to add an attribute value which is already present within the entry, no error occurs.
After the execution of the modify operation, the value appears twice in the entry instead.

As a consequence, it is possible for instance to create an entry like this:

---

dn: cn=Stefan Zoerner,ou=users,ou=system
sn: Zoerner
objectClass: top
objectClass: top
objectClass: person
cn: Stefan Zoerner

---

Expected behavior is error code 20, which indicates that the attribute value specified in a modify or add operation already exists as a value for that attribute.
I will add a test case as usual which demonstrates the bug with a person entry.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Stefan Zoerner added a comment - 01/Sep/05 07:03 AM
Here is a test case, which demonstrates the error with the description attribute of a person entry. But the bug occurs with other attributes, even objectClass as well. The critical method is testAddExistingAttributeValue, which fails.

Alex Karasulu added a comment - 13/Sep/05 12:41 AM
Committed in revision 289356 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=280356

Stefan Zoerner added a comment - 15/Sep/05 08:19 PM
I have rebuilded the server, and tested the behavior programmatically (test cases) and with a GUI client. The described error does not occur any more, therefore I close the issue.