[ 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
