Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 87385 invoked from network); 8 Sep 2009 09:58:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Sep 2009 09:58:55 -0000 Received: (qmail 66584 invoked by uid 500); 8 Sep 2009 09:58:55 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 66553 invoked by uid 500); 8 Sep 2009 09:58:55 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 66542 invoked by uid 99); 8 Sep 2009 09:58:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2009 09:58:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mrduguo@gmail.com designates 209.85.220.210 as permitted sender) Received: from [209.85.220.210] (HELO mail-fx0-f210.google.com) (209.85.220.210) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2009 09:58:44 +0000 Received: by fxm6 with SMTP id 6so2379265fxm.43 for ; Tue, 08 Sep 2009 02:58:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=TYSb+5MDNInxyhZt2Lg0Q3rmKnJDGatNAykJdqFixXo=; b=nWoKQPVt5xIWUghmyimDeFCirZgvo5GoxS7Cd3IWKSTxDF1zE7o5REIv12lmBdbPgg sqPrT+I+S0tek1l0MWpOmIUrxybFpHyZUaSG4c26vuaPZ/ff9dPynEeyeZy7XxbCmPvW ksBfK3NuVzIKrMgy+Yi4qbtbK0SqSEhhPJOgE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=R+6r7nNyc9VgW6NyFvzcPOTFN3qBke8k8HekeFgSAzQj+yJjUnbackQLClTrt6yM36 x2JQYE0guwlSh4b1NDfOAIyOufueKEy3kJ3k/5jHstxnp9uY1r9hv8tIWtdHe6S8XjlQ y+jYhuyuPCIUDoEr4Wc9x3man/UGr0l7PyUT0= MIME-Version: 1.0 Received: by 10.204.13.198 with SMTP id d6mr13087020bka.188.1252403904291; Tue, 08 Sep 2009 02:58:24 -0700 (PDT) In-Reply-To: <2bc800bc0909080225p7cbf837cy95a38220d3e34f9c@mail.gmail.com> References: <2bc800bc0909080201h762d7120n2017f1e6f75f5eda@mail.gmail.com> <510143ac0909080205w4f358ed9k33f678c0b5e32710@mail.gmail.com> <2bc800bc0909080225p7cbf837cy95a38220d3e34f9c@mail.gmail.com> Date: Tue, 8 Sep 2009 10:58:24 +0100 Message-ID: Subject: Re: Refresh problem From: Guo Du To: users@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Sep 8, 2009 at 10:25 AM, mitziuro 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