Hi Sebastien, On Fri, Oct 28, 2011 at 4:39 AM, Sébastien Bahloul <[email protected]> wrote: > Hi guys, > > First of all, just a word to say thank you about the great job you're doing > ! > > I'm looking to the API and I found several things that should look bizarre > or not enough documented : > - I was not able to find a smart way to check for results availability when > search asynchronously: I need to call > SearchFuture.get(1, TimeUnit.NANOSECONDS) which will launch an exception if > no entry has been already sent back to the client. do you have a test case to reproduce > - on the PersistentSearchControl, it is not clear the meaning and usage > of ChangeType.ADD regarding ChangeType.ADD_VALUE > - LdapConnection.search() methods return a Cursor<SearchResponse> which is > the generic type of SearchCursor. Could it be possible to change the > Exception returns by SearchCursor.get() to provide a more specific error > because it returns now a java.lang.Exception > > If someone of you guys has a minute to give some explanations, it will be > welcomed. > which version of API you are using, I didn't find any of these in the latest snapshot of 1.0.0-M9 (unreleased) can you try with the released version 1.0.0.-M8 and tell us > The final target is to move the LSC project to Apache Directory API, and as > you may have understood, I'm currently moving the Syncrepl plugin from > Unbounded ID to Apache Directory API. > interesting project, will explore more in the coming days.
thanks for using Apache LDAP API > Kind regards, > -- > Sebastien BAHLOUL > IAM / Security specialist > Ldap Synchronization Connector : http://lsc-project.org > Blog : http://sbahloul.wordpress.com/ > -- Kiran Ayyagari
