Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 8392 invoked from network); 2 Jul 2008 16:05:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jul 2008 16:05:29 -0000 Received: (qmail 21273 invoked by uid 500); 2 Jul 2008 16:05:28 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 21259 invoked by uid 500); 2 Jul 2008 16:05:28 -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 21248 invoked by uid 99); 2 Jul 2008 16:05:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2008 09:05:28 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Brett.Conoly@digitalinsight.com designates 67.135.240.36 as permitted sender) Received: from [67.135.240.36] (HELO ATLIMS02.corp.ad.diginsite.com) (67.135.240.36) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2008 16:04:38 +0000 Received: from atlexf01.corp.ad.diginsite.com ([172.18.114.73]) by ATLIMS02.corp.ad.diginsite.com with InterScan Message Security Suite; Wed, 02 Jul 2008 12:04:56 -0400 Received: from athexm01.corp.ad.diginsite.com ([172.18.124.136]) by atlexf01.corp.ad.diginsite.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Jul 2008 12:04:13 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Jackrabbit Caching? Date: Wed, 2 Jul 2008 12:04:13 -0400 Message-ID: <7E79528FEA116746A9B896C817C51E5B02D57CD6@athexm01.corp.ad.diginsite.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Jackrabbit Caching? Thread-Index: Acjbwf+at5Dy3T3bS56PXodtycJFQAAfc/ixAAcsdpA= References: <510143ac0807011432p5de0ad52q7a49baa873b6e1c7@mail.gmail.com> From: "Conoly, Brett" To: X-OriginalArrivalTime: 02 Jul 2008 16:04:13.0895 (UTC) FILETIME=[45AACD70:01C8DC5D] X-Virus-Checked: Checked by ClamAV on apache.org 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. Brett -----Original Message----- From: Jared Graber [mailto:jared.graber@IACcap.com]=20 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? -Jared -----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? =20 Hi, On Wed, Jul 2, 2008 at 12:13 AM, Jared Graber wrote: > 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. BR, Jukka Zitting