directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRAPI-35) LdapConnection.search(...) methods should return a SearchCursor instead of a Cursor object in order to allow access to the SearchCursor.getSearchResultDone() method
Date Fri, 22 Oct 2010 12:04:16 GMT
LdapConnection.search(...) methods should return a SearchCursor instead of a Cursor object
in order to allow access to the SearchCursor.getSearchResultDone() method
--------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: DIRAPI-35
                 URL: https://issues.apache.org/jira/browse/DIRAPI-35
             Project: Directory Client API
          Issue Type: Improvement
    Affects Versions: 0.2.0
            Reporter: Pierre-Arnaud Marcelot
             Fix For: 0.2.0


While using the API inside Studio, I need to get the SearchResultDone from the cursor.

First I was expecting it via the 'hasMore()' and 'next()' methods but it is excluded from
those methods which makes sense in such a high level api.

A 'getSearchResultDone()' method exists in the SearchCursor class implementing the Cursor
interface.

Unfortunately as the LdapConnection.search(...) methods are typed with a Cursor object as
return type, I can't access this information (without a cast)

It would be great to introduce a SearchCursor interface used as return type of the search(...)
methods and which extends the Cursor interface and adds definition of the getSearchResultDone()
method.

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


Mime
View raw message