You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Nicolas Toper (JIRA)" <ji...@apache.org> on 2006/08/09 00:18:16 UTC
[jira] Created: (JCR-535) Ignore root node when importing through
sysView
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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12426891 ]
Stefan Guggisberg commented on JCR-535:
---------------------------------------
you're right, i reread section 7.3.8 and agree with you that we currently don't handle IMPORT_UUID_COLLISION_REPLACE_EXISTING on import of jcr:root.
we should implement IMPORT_UUID_COLLISION_REPLACE_EXISTING for jcr:root properly rather than skipping jcr:root.
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12445194 ]
Stefan Guggisberg commented on JCR-535:
---------------------------------------
> About this issue, can I assume there are no concurrent operations?
no. why would you assume that?
>
> I am deleting all subnodes under root except jcr:system. The issue I see is a session creating some nodes while I delete them all. I think this could happen and this should be taken care of.
>
> Are my assumptions correct?
for the former: yes
for the latter: no
importXML has different sematics than a 'restore' operation. for an import you don't need exclusive access.
>
> If yes, how could I manage to handle this issue?
>
> 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, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.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
[jira] Updated: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-535:
------------------------------
Status: Patch Available (was: Open)
> Ignore root node when importing through sysView
> -----------------------------------------------
>
> Key: JCR-535
> URL: https://issues.apache.org/jira/browse/JCR-535
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Nicolas Toper
> Priority: Minor
> Attachments: patch-1-Ignore-root-node.txt, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.txt, WorkspaceImporterRootNodeTest.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12426884 ]
Stefan Guggisberg commented on JCR-535:
---------------------------------------
Session#importXML and Workspace#importXML are JCR API methods.
the suggested modification is not compliant with the spec.
-1 for the proposed modification
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12426892 ]
Jukka Zitting commented on JCR-535:
-----------------------------------
> 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.
Note that Nicolas explicitly excludes jcr:system from the backup export, so it isn't being imported. Thus there should be no problem with implementing the "getNode, change, save" cycle for importing jcr:root with REPLACE_EXISTING as specified in 7.3.8.
You are right in that the REPLACE_EXISTING is defined to remove the entire replaced subtree, includin in this case /jcr:system, but I think the same logic as we use to prevent modification of protected properties and child nodes in normal imports applies here as well, i.e. the /jcr:system subtree doesn't get removed since it's protected.
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Nicolas Toper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12444311 ]
Nicolas Toper commented on JCR-535:
-----------------------------------
Sure. Let me write it. I'll post it this week.
> 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, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12426887 ]
Jukka Zitting 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.
> 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
[jira] Updated: (JCR-535) Ignore root node when importing through
sysView
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=all ]
Stefan Guggisberg updated JCR-535:
----------------------------------
Comment: was deleted
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "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
[jira] Updated: (JCR-535) Ignore root node when importing through
sysView
Posted by "Nicolas Toper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=all ]
Nicolas Toper updated JCR-535:
------------------------------
Attachment: WorkspaceImporterRootNodeTest.patch
Hi,
Here is a test code demonstrating the issue and that it applies only to REPLACE_EXISTING behaviour.
Nicolas
> 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, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.txt, WorkspaceImporterRootNodeTest.patch
>
>
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Nicolas Toper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12443580 ]
Nicolas Toper commented on JCR-535:
-----------------------------------
Understood :) Thanks. So I'll check the UUID (imagine a use case where we swap one JCR compliant repository for another; if I remind the spec correctly the root node UUID can be different in both repository).
One issue is still unclear: do I delete simply all nodes in the subtree?
What about protected nodes? (/jcr:system will be explicitely excluded from the removal of course)
> 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
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Nicolas Toper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12444926 ]
Nicolas Toper commented on JCR-535:
-----------------------------------
Hi,
About this issue, can I assume there are no concurrent operations?
I am deleting all subnodes under root except jcr:system. The issue I see is a session creating some nodes while I delete them all. I think this could happen and this should be taken care of.
Are my assumptions correct?
If yes, how could I manage to handle this issue?
> 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, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.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
[jira] Updated: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-535:
------------------------------
Resolution: Won't Fix
Assignee: Jukka Zitting
Status: Resolved (was: Patch Available)
Resolving as Won't Fix in favour of the recent work in JCR-442.
> Ignore root node when importing through sysView
> -----------------------------------------------
>
> Key: JCR-535
> URL: https://issues.apache.org/jira/browse/JCR-535
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Nicolas Toper
> Assignee: Jukka Zitting
> Priority: Minor
> Attachments: patch-1-Ignore-root-node.txt, patch-WorkspaceImporter-231006-2.txt, patch-WorkspaceImporter-231006.txt, patch-WorkspaceImporterTest-231006.txt, WorkspaceImporterRootNodeTest.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-535) Ignore root node when importing through
sysView
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-535?page=comments#action_12443657 ]
Jukka Zitting commented on JCR-535:
-----------------------------------
> One issue is still unclear: do I delete simply all nodes in the subtree?
The replace operation is specified to replace the entire subtree, so a full delete followed by a normal import should do it.
> What about protected nodes? (/jcr:system will be explicitely excluded from the removal of course)
I think /jcr:system is the only part that should remain in place when replacing the root, at least in Jackrabbit.
> 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