directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Resolved: (DIREVE-232) Modify operation (removal) provides wrong return codes in two situations.
Date Mon, 29 Aug 2005 05:09:04 GMT
     [ ]
Alex Karasulu resolved DIREVE-232:

    Resolution: Fixed

Committed test case and fixes in revision 264063 here:

> Modify operation (removal) provides wrong return codes in two situations.
> -------------------------------------------------------------------------
>          Key: DIREVE-232
>          URL:
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 0.9.2
>  Attachments:
> 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:
For more information on JIRA, see:

View raw message