Hi, What about making the backend read-only?
Regards, Thomas On Thu, Feb 12, 2009 at 9:06 AM, Michael Wechner <[email protected]>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-d...@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 >
