[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12426888 ] Stefan Guggisberg commented on JCR-535: ---------------------------------------
> I don't think we currently implement the IMPORT_UUID_REPLACE_EXISTING > behaviour > for jcr:root as specified in section 7.3.8. Implementing that would solve > Nicolas' problem > in a standards compliant manner. no, it wouldn't. we deliberatly don't allow to replace the root node. /jcr:system e.g. is protected, and for a good reason so because it's system managed and not user editable. the importXML methods were never intended to serve as restore operations for system managed data. > Ignore root node when importing through sysView > ----------------------------------------------- > > Key: JCR-535 > URL: http://issues.apache.org/jira/browse/JCR-535 > Project: Jackrabbit > Issue Type: Improvement > Components: core > Reporter: Nicolas Toper > Priority: Minor > Attachments: patch-1-Ignore-root-node.txt > > > When importing through a sysView, we should ignore the root node. It is in > the sysView to provide a root XML node, but the importer is going to attach > it to the repository"s root node... Which would create another root node and > often raise exception. This is a know issue > I needed this behavior to change for the backup tool, since I use the > sysView. Therefore, I havce slightly updated the WorkspaceImporter. Maybe I > should update too the SessionImporter so we have a consistant behavior. What > do you think? -- 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
