jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-442) Implement a backup tool
Date Mon, 26 Jun 2006 17:12:31 GMT
    [ http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12417844 ] 

Tobias Bocanegra commented on JCR-442:

some thoughts:
- why needs BackupConfig.init() the repositoryimpl ? i would do a Config.getBackup(repo) instead.
- you don't need to call super() in the Backup class, since it extends from Object.
- if config creates backup, why do you need to pass config to save() ? (and why not passing
one to restore?)
- if config.getBackup() returns a Backup, why does RepositoryImpl.getBackupRepository() return
a BackupRepository ?

> Implement a backup tool
> -----------------------
>          Key: JCR-442
>          URL: http://issues.apache.org/jira/browse/JCR-442
>      Project: Jackrabbit
>         Type: New Feature

>     Reporter: Jukka Zitting
>  Attachments: patch
> 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:
For more information on JIRA, see:

View raw message