[jira] Commented: (JCR-535) Ignore root node when importing through sysView

["Nicolas Toper (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12443540 ] 
            
Nicolas Toper commented on JCR-535:
-----------------------------------

Hi,

Here is what the spec states about importing root node in Workspace.importXML() (with a system view):

"IMPORT_UUID_COLLISION_REPLACE_EXISTING: This setting is
equivalent to importing into the Session and then calling save
since save always operates according to UUID (plus relative path,
for non-referenceables). In both cases the result is that the root
node of the workspace will be replaced along with its subtree (i.e.,
the whole workspace), just as if the root node had been altered
through the normal getNode, change, save cycle."

Just to make sure I have understood it correctly, this means root UUID can be altered in JR if we implement it. Am I correct? If yes, is it OK for JR (I thought this specific UUID was hard coded)?

Also if we implement it, what about protected node, should they be removed too? (/jcr:system will be explicitely excluded from the removal of course)

Thanks for your explanations :)
 
Nico

> 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