Hi John, as you noted, copying and merging on application level is not a full replacement of workspaces. I would not even call it “emulation”.
Could you provide more information on what the problem is you want to solve? Maybe there are other possibilities. Cheers Michael > On 29 Dec 2014, at 17:36, John Gretz <[email protected]> wrote: > > Hi guys, > Given that at this time Oak supports only a single workspace - are there any > generally decent strategies to emulate multiple worspaces in Oak? > I think there was a suggestion in another email thread to copy the content > tree for each author and use ACLs to control access. How would this strategy > work during a merge back into the main tree - 'copy' does not preserver the > UUIDs the same way a workspace 'clone' would in Jackrabbit... > Thanks!-John
