jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mitziuro <mitzi...@gmail.com>
Subject Re: Refresh problem
Date Tue, 08 Sep 2009 09:25:16 GMT
On Tue, Sep 8, 2009 at 12:05 PM, Jukka Zitting <jukka.zitting@gmail.com>wrote:

> Hi,
> On Tue, Sep 8, 2009 at 11:01 AM, mitziuro<mitziuro@gmail.com> 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
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) ?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message