[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12443545 ] Jukka Zitting commented on JCR-535: -----------------------------------
No, the root UUID can't be altered, but you should be able to import an XML document with IMPORT_UUID_COLLISION_REPLACE_EXISTING that contains a jcr:root element with the correct UUID, and have the import replace the workspace contents. Note that the root node is currently not referenceable by default, so this would only work if we changed the default or if an administrator explicitly added the mix:referenceable mixin to the root node. > 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
