Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: jackrabbit-commits@incubator.apache.org
Date: Tue, 13 Jun 2006 22:10:21 -0000
Message-ID: <20060613221021.23702.89504@ajax.apache.org>
Subject: [Jackrabbit Wiki] Update of "BackupTool" by Nico

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by Nico:
http://wiki.apache.org/jackrabbit/BackupTool

------------------------------------------------------------------------------
  
  -	Other resources (custom node types and namespaces) are saved and serialized using Jackrabbit's internal xml node type serialization format (NodeTypeWriter and NodeTypeReader for instance).
  
+ - We would then zip everything in the working folder move it as a stream to RepositoryImpl. 
+ 
  
  == Locking strategy ==
  
@@ -109, +111 @@

  
  Special classes: BackupAllWorkspaces and BackupNodeVersionHistories link directly to BackupWorkspace for simplicity purposes.
  
+ BackupRepositoryConfig backup the repository.xml file and the properties file. If there is one for the workspace we will use it.
+ 
  I can see for now two design patterns: a Builder slightly modified and a Facade.
  
  == Next Steps ==
@@ -123, +127 @@

  === Evolution ===
  After the first release, here are some evolutions ideas
  
+  * Remove the need for the working folder. Use only streams.
   * Add a remote client using either a dedicated RMI connection or the JCR one.  
   * Add support later for a restore operation while the repository is still in operation by rewriting the local restore operation and its client.
   * Hotbackup (see post on the ML on this subject)