On Mon, Jul 22, 2013 at 4:52 PM, Alexander Broekhuis <a.broekh...@gmail.com>wrote:
> Hi, > > Thanks for the quick reply. > > > > > > > > you get the results asynchronously, i.e, you leave the loop running and > > it > > will wait for > > the incoming results, just make sure you increase the timeout either at > the > > connection (setTimeOut) > > level or in the SearchRequest (setTimeLimit()) > > > > Thanks for the explanation. So this means I have to create a thread myself > to handle changes etc. Also, in my test, existing entries are not part of > the result, is this intended? In other words, I have to do a "normal" query > for existing entries, and the persistent one for changes? > > by setting the changesOnly flag ( setChangesOnly(false)) to false you can get all the entries as well (but appears that this flag is ignored now ) > Is there any helper class in the Ldap API which makes this simpler for me > to use? For example a listener model with callback methods? > no, but take a look at the searchAsync() method and see if the returned Future can be used according to your use > > -- > Met vriendelijke groet, > > Alexander Broekhuis > -- Kiran Ayyagari http://keydap.com
