[ http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12425758 ] Jukka Zitting commented on JCR-442: -----------------------------------
Marcel: > Regarding repository descriptors, I'm not sure if it makes sense to actually > try to restore them. > Most of those descriptors are tightly coupled with the internals of an > implementation and it's > capabilities and are therefore read-only. e.g. whether versioning is > supported, etc. That's true, but the descriptors can also be used to convey custom information, for example the name and contact details of the repository administrator. Jackrabbit doesn't directly support this at the moment, but I think it would be a nice feature to add at some point. Then backing up and restoring that data would make a lot of sense. In fact the setDescriptors() method even effectively implements this feature, now we just need to come up with some semi-standard descriptor keys. Of course "restored" descriptor should never override the standard descriptors, but Nicolas' implementation already takes care of this by calling setDefaultRepositoryProperties(). > 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-backup-060803.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.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
