jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SalmasCM <sal...@criticalmass.com>
Subject Re: Urgent issue with deleting clined nodes
Date Fri, 24 Apr 2009 03:09:11 GMT

My problem is solved. I needed to delete the node in the master workspace and
then save that session and call update to sync the removal over to the
second session.


SalmasCM wrote:
> 
> We import our data using XML files. 
> topNode.remove(); //remove the top node in the XML file.
> session.importXML("/", stream,
> ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING);
> 
> After the import I clone the node
> 
> toSession.getWorkspace().copy(wsFromName, path, path);
> 
> Each file imports a section of the site. Sometimes a section may need to
> be reloaded. I then need to delete the node from both workspaces and call
> the import code again and I get
> 
> javax.jcr.ItemNotFoundException: cc3b54f9-9283-4479-b60f-d77b264c1aa3
> 
> However, if I don't delete the node prior to the import then the data gets
> imported twice and I get topNode and topNode[1] in my database.
> 
> How can I delete a cloned node across both workspaces or do the XML import
> and have it replace the top node instead of appending a new one?
> 

-- 
View this message in context: http://www.nabble.com/Urgent-issue-with-deleting-clined-nodes-tp23197339p23209012.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Mime
View raw message