jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Toper (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-442) Implement a backup tool
Date Wed, 16 Aug 2006 17:55:16 GMT
     [ http://issues.apache.org/jira/browse/JCR-442?page=all ]

Nicolas Toper updated JCR-442:
------------------------------

    Attachment: patch-jr-final1.tar.gz

This is the proposed path to the core for the backup tool.

Sorry for the 4 patches but some Gremlins have invaded my computer and created a lot of problem
with SVN.

Here are the modifications I propose:

- Update to PropInfo. 
Please see relevant thread on ML. 

- Update to VersionManagerImpl and to RepositoryImpl. 
In order to restore the NodeVersionHistories, I need to gain access to the VersionManagerImpl
persistence (through a getter) manager. For this, I need to put the getVersionManager() of
RepositoryImpl in public  (I couldn't use the one from SessionImpl since there can be a XAVersionManager
and the cast to VersionManagerImpl doesn't work in this case)

- Add a NodeVersionHistoriesUpdatableStateManager
It is a specific UpdatableStateManager designed specifically to update the NodeVersionHistories.
It is heavily based on the LocalItemStateManager.

I have to be able to connect the imported NodeState so I had to put this class in the o.a.j.core.state
package and couldn't put it in the backup one. (connect is protected to state and it is *really*
a bad idea to put in public).

The idea was to be able to work with a BatchedItemOperation class so to keep as much as possible
its original semantic.

I am sure there is a better way to handle those needs instead of updating the core but I didn't
find any yet. 

As soon, as we all agree, I will update the relevant part of my code (in backup and in this
patch) and document them properly.

Cheers,
Nico
PS I am cleaning up my SVN so next time, I can post one patch for all.

> Implement a backup tool
> -----------------------
>
>                 Key: JCR-442
>                 URL: http://issues.apache.org/jira/browse/JCR-442
>             Project: Jackrabbit
>          Issue Type: New Feature
>            Reporter: Jukka Zitting
>         Attachments: backupTool-final1.tar.gz, jackrabbit-1.patch.txt, patch, patch-060808-backup.txt,
patch-backup-060716.txt, patch-backup-060719.txt, patch-backup-060725.txt, patch-backup-060726.txt,
patch-backup-060728.txt, patch-backup-060803.txt, patch-backup-090806.txt, patch-jackrabbit-060716.txt,
patch-jackrabbit-060718.txt, patch-jackrabbit-060725.txt, patch-jackrabbit-060726.txt, patch-jackrabbit-060728.txt,
patch-jr-060803.txt, patch-jr-final1.tar.gz, patch.txt, patch.txt, patch.txt, patch.txt
>
>
> Issue for tracking the progress of the Google Summer of Code project assigned to Nicolas
Toper.  The original project requirements are:
> "Implement a tool for backing up and restoring content in an Apache Jackrabbit content
repository. In addition to the basic content hierarchies, the tool should be able to efficiently
manage binary content, node version histories, custom node types, and namespace mappings.
Incremental or selective backups would be a nice addition, but not strictly necessary."

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message