Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of tmueller@day.com designates
 207.126.148.183 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4993D87A.6070707@wyona.com>
References: <4993D87A.6070707@wyona.com>
Date: Thu, 12 Feb 2009 09:15:21 +0100
Message-ID: <91f3b2650902120015n2b8d49f3m5d1c9565391615d6@mail.gmail.com>
Subject: Re: Lock/Block write access in order to maintenance of the repository
From: =?ISO-8859-1?Q?Thomas_M=FCller?= <thomas.mueller@day.com>
To: users@jackrabbit.apache.org
Content-Type: multipart/alternative; boundary=001636c5990c4e72df0462b4521f

--001636c5990c4e72df0462b4521f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

What about making the backend read-only?

Regards,
Thomas


On Thu, Feb 12, 2009 at 9:06 AM, Michael Wechner
<michael.wechner@wyona.com>wrote:

> Hi
>
> In order to do some "maintenance" of my Jackrabbit/JCR based repo during
> production (for example migrating to another repo implementation) I would
> like to block/lock all write access. Is there some simple "switch"? And if
> so, how does my application know about it (such that it can communicate it
> to the end-user)?
>
> I have been searching and found the following
>
>
> http://www.nabble.com/Snapshot-of-local-data-(in-sync-with-DB)-td19924825.html<http://www.nabble.com/Snapshot-of-local-data-%28in-sync-with-DB%29-td19924825.html>
>
> http://mail-archives.apache.org/mod_mbox/jackrabbit-commits/200811.mbox/%3C472701467.1227186960024.JavaMail.www-data@brutus%3E
>
> but it's not really clear to me and how to make use of it.
>
> Any other pointers/hints are much appreciated
>
> Thanks
>
> Michael
>

--001636c5990c4e72df0462b4521f--