[ 
http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12424028 ] 
            
Jukka Zitting commented on JCR-442:
-----------------------------------

Committed patch-backup-060728.txt in revision 426435 with some modifications:

* Made the paths in BackupTest relative

* Use Repository.getDescriptorKeys() and Repository.getDescriptor(String) to 
access repository properties instead of using the internal loadRepProps method. 
Thus, no need to modify RepositoryImpl.

* Use a SysViewSAXEventGenerator subclass that skips /jcr:system in 
WorkspaceBackup. Thus, no need to modify SessionImpl and the SAXEventGenerators.

* Depend on RepositoryConfigurationParser for the PERSISTENCE_MANAGER_ELEMENT 
constant in BackupConfigurationParser. It's a bit ugly, but avoids the need to 
have the constant in ConfigurationParser. Thus, no need to modify the 
ConfigurationParsers.

These modifications remove all needs to modify jackrabbit-core, so I won't be 
applying patch-jackrabbit-060728.txt. :-)

I ran the backup test and received a nice backup ZIP file. Looking good so far!

> 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: jackrabbit-1.patch.txt, patch, patch-backup-060716.txt, 
> patch-backup-060719.txt, patch-backup-060725.txt, patch-backup-060726.txt, 
> patch-backup-060728.txt, patch-jackrabbit-060716.txt, 
> patch-jackrabbit-060718.txt, patch-jackrabbit-060725.txt, 
> patch-jackrabbit-060726.txt, patch-jackrabbit-060728.txt, 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

        

Reply via email to