jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conoly, Brett" <Brett.Con...@digitalinsight.com>
Subject RE: Jackrabbit Caching?
Date Wed, 02 Jul 2008 16:04:13 GMT
I don't know how you're actually retrieving the content but I had this
problem retrieving data from webdav a while back.  I did learn that the
headers sent back by webdav are not updated unless you set the
JCR_LASTMODIFIED property of the content node.  This prevented the
caching for me, hope this helps.

-----Original Message-----
From: Jared Graber [mailto:jared.graber@IACcap.com] 
Sent: Wednesday, July 02, 2008 8:55 AM
To: users@jackrabbit.apache.org
Subject: RE: Jackrabbit Caching?

I understand that I shouldn't modify the underlying database directly,
but I need to deal w/ database restores.
So is there a way to turn off caching?


-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitting@gmail.com]
Sent: Tue 7/1/2008 5:32 PM
To: users@jackrabbit.apache.org
Subject: Re: Jackrabbit Caching?

On Wed, Jul 2, 2008 at 12:13 AM, Jared Graber <jared.graber@iaccap.com>
> Is the in-memory cache preventing me from getting the new data?

Only if you modify the underlying database directly, which you should
never do.

If you only access the content through the JCR API, Jackrabbit will
automatically make sure that all caches are correctly invalidated and
search indexes updated whenever content changes.

Furthermore, since the JCR-RMI layer does no caching you can also use
that without worrying about cache coherence issues.


Jukka Zitting

View raw message