On Wed, Aug 6, 2008 at 1:58 PM, Matthijs Wensveen <[EMAIL PROTECTED]> wrote: > Hi, > > Our application imports content in one workspace and when it's done and > everything is verified the content is cloned to the default workspace. At > the top of the freshly imported content is one node with a rather large > subtree (10.000+ nodes). More than occasionally the clone operation fails > because the jvm runs out of heap space. Are there any alternatives to clone > that do not put the entire tree in memory before writing it to the other > workspace?
Well, you could clone only sub-parts (if that is possible) or simply copy node-by-node and save every X nodes, so the memory footprint is not that big. Regards, Alex -- Alexander Klimetschek [EMAIL PROTECTED]
