You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2010/10/22 14:04:16 UTC
[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
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.
[jira] Closed: (DIRAPI-35) LdapConnection.search(...) methods
should return a SearchCursor instead of a Cursor object in order to allow
access to the SearchCursor.getSearchResultDone() method
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRAPI-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot closed DIRAPI-35.
----------------------------------------
Resolution: Fixed
Assignee: Pierre-Arnaud Marcelot
Fixed at revision 1027982.
http://svn.apache.org/viewvc?rev=1027982&view=rev
> 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
> Assignee: 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.