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 Tue, 25 Jul 2006 21:31:15 GMT
     [ http://issues.apache.org/jira/browse/JCR-442?page=all ]

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

    Attachment: patch-jackrabbit-060725.txt

Update to JR core in order to achieve Backup. Here are the modifications:
- RepositoryImpl: getNodeTypeRegistry is now public +  Properties loadRepProps() + public
String[] getWorkspaceNames() public getSystemSession()
- added in RepositoryImpl WorkspaceConfig getWorkspaceConfig(String workspaceName)
- NodeTypeRegistry: added method public NodeTypeDef[] getRegisteredNodesTypesDefs()
- Any tabs issues? (I found some in some files I didn't update so I didn't dare to replaceAll
"regexpically")
- class SystemSession is now public

Maybe I have put too many classes in public. Please tell me...

> 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-jackrabbit-060716.txt, patch-jackrabbit-060718.txt, patch-jackrabbit-060725.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

        

Mime
View raw message