[ http://issues.apache.org/jira/browse/DIREVE-232?page=all ] Stefan Zoerner closed DIREVE-232: ---------------------------------
I have retested the functionality in the current version. The server exhibits the expected behavior to the client, therefor I close this issue now. Thank you Alex for painting two of my test cases green! > Modify operation (removal) provides wrong return codes in two situations. > ------------------------------------------------------------------------- > > Key: DIREVE-232 > URL: http://issues.apache.org/jira/browse/DIREVE-232 > Project: Directory Server > Type: Bug > Versions: 0.9.2 > Reporter: Stefan Zoerner > Assignee: Alex Karasulu > Priority: Minor > Fix For: 0.9.2 > Attachments: ModifyRemoveTest.java > > The modify operation provides wrong return codes in two cases: > 1. Removal of an attribute which does not occur in the entry (expected result > is error code 16: noSuchAttribute) > 2. Removal of an invalid attribute, i.e. not existing within the schema > (expected result is error code 17: undefinedAttributeType) > This is quite similar to DIREVE-226. > I attach a subclass of AbstractServerTest which contains several test methods > for basic removal ops. Due to the recent changes regarding schema checks, > most of them succeed. Two tests check for the return codes above (and fail). > It includes also a test which deletes a required attribute (not part of RDN), > which fails -- but this is expected due to the current development progress. -- 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
