You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/12/16 15:36:30 UTC
[jira] [Issue Comment Edited] (JCR-3184) extend ConsistencyChecker
API to allow adoption of orphaned nodes to a to-be-specified parent node
[ https://issues.apache.org/jira/browse/JCR-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170990#comment-13170990 ]
Julian Reschke edited comment on JCR-3184 at 12/16/11 2:34 PM:
---------------------------------------------------------------
(work in progress, activation through PM config currently missing)
This patch adds the "adoption" functionality, but leaves the choice of where to move the nodes to the caller.
was (Author: reschke):
(work in progress, activation through PM config currently missing)
> extend ConsistencyChecker API to allow adoption of orphaned nodes to a to-be-specified parent node
> --------------------------------------------------------------------------------------------------
>
> Key: JCR-3184
> URL: https://issues.apache.org/jira/browse/JCR-3184
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Attachments: JCR-3184.diff
>
>
> The optional ConsistencyChecker API on persistence managers allows analyzing and fixing storage inconsistencies. The current fixup code though does not attempt to "adopt" orphaned nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira