You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2010/05/28 14:47:37 UTC

[jira] Closed: (DIRSERVER-1173) Delete operation with a PersistentSearch returns the deleted entry

     [ https://issues.apache.org/jira/browse/DIRSERVER-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari closed DIRSERVER-1173.
-------------------------------------

    Resolution: Fixed

The reported problem no longer exists, closing the issue.

> Delete operation with a PersistentSearch returns the deleted entry
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-1173
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1173
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.2
>            Reporter: Emmanuel Lecharny
>            Assignee: Kiran Ayyagari
>             Fix For: 2.0.0-RC1
>
>
> While debugging a failure in PersistentSearch I found that we have an inconsistant behavior when deleting entries :
> testPsearchDelete :
>   ctx.destroySubcontext( RDN ); // RDN = "cn=Tori Amos"
>   ...
>   assertNotNull( listener.result );  // Should be null, but is not
>   assertEquals( RDN, listener.result.getName() );   // Contains the deleted entry...
> Another test :
> testPsearchAbandon :
>   ctx.destroySubcontext( "cn=Jack Black" );
>   ...
>   // there seems to be a race condition here
>   //assertNull( listener.result ); // Has been commented as otherwise, the test would fail
>   ...
> Note the comment...
> While looking into the PersistentSearchListener code, here is what we have :
>     public void objectRemoved( NamingEvent evt )
>     {
>         // send the entry back
>         sendEntry( evt );
>     }
> This sendEntry method simply return the deleted entry, and is supposed to set the PersistentSearchControl, so the test is incorrect. We should test that the Control contains the correct ChangeType
>   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.