On Tue, Sep 8, 2009 at 10:25 AM, mitziuro<[email protected]> wrote: > After i'm changing the path with session.move, i'm doing a search with > xPath. > If i do the search in the next second after the event i don't see that node. > If i refresh i see it. > For 20+ nodes the situation is worse because i get partial results in the > next seconds after i moved the nodes. > Is there a way to change this behaviour (don't block the nodes for listing > or something else) ? > Thanks > It designed to work like this. The index for search is running on background and it's not guaranteed to work immediately after you do any changes to the nodes.
Instead of using search api, you may traverse nodes with children to avoid unexpected result. Regards, -Guo
