Hi Cédric,

On Wed, 2024-11-13 at 17:24 +0100, Cédric Damioli wrote:
> Hello,
> 
> Our product is build on top of Jackrabbit since the early days (20
> years 
> now!), and I'm in the very beginning of the process of testing the 
> migration to Oak.
> 
> We currently rely on two features which I don't find in oak:
> 
>   - multiple workspaces. It has been discussed many times here. I 
> suppose that the solution is to actually have as many oak
> repositories 
> as there was Jackrabbit workspaces ? It comes with a little overhead,
> but I suppose I can live with that. Or are there a better known
> solution?
> 
>   - NodeImpl#addNodeWithUuid. In my multiple workspaces scenario, I
> need 
> that "corresponding" nodes have the same UUIDs, and the Jackrabbit 
> methods works perfectly in that scenario. Is there a replacement in
> Oak 
> ? I could also come with a PR adding the same method in oak's
> NodeImpl, 
> as well as another helper in TreeUtil#addChild to help creating a
> Node 
> with a given UUID. What do you think ?
> 


I am not close to Oak core development, but it looks like your second
question assumes multiple workspaces, right? If you migrate your
application to Oak you will not have the same UUID for multiple nodes
in the same workspace so linking between nodes will have to be done
differently.

I think it boils down to why you currently use workspaces and how you
could replace those with standard Oak approaches.

Multiple repositories is one option. Different sub-trees is another
approach.

Thanks,
Robert

> Thanks in advance for your answers,
> Regards,
> Cédric

Reply via email to