On Tue, Sep 8, 2009 at 12:05 PM, Jukka Zitting <[email protected]>wrote:
> Hi, > > On Tue, Sep 8, 2009 at 11:01 AM, mitziuro<[email protected]> wrote: > > Everytime i change the path of a node, the node is blocked for listing > > until jackrabbit makes some calculations. > > For example if i have 20 nodes it takes a while after i've changed the > path > > to list all of them. > > Is there a way to avoid that? > > I'm not sure what you're after here. Obviously Jackrabbit needs some > time to persist any changes and load modified information, but in > normal use this is pretty fast. > > Can you be a bit more specific? What are doing (sample code) and what > kind of performance you are expecting/seeing? > > BR, > > Jukka Zitting > 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
