Hi,
Has anyone experience in using mix:shareable with Magnolia?
For background I was looking for a way for a page (or more likely page hierarchy) to exist in different parts of the site and was thinking that something like symbolic links in (linux/unix) filesystem would work nicely. And of course there is a concept called mix:shareable in JCR (since 2.0) that makes it possible to add same nodes (clone w/ same uuid) under different parents.
I tested this with some groovy scripts and was able to add shareable nodes in website workspace and AFAIK it actually works. I can edit one node and changes are reflected in the "shared clone". Only things that I found out do not handle this are magnolia admin apps (Pages / JCR browser) as it seems that, at least tree view, internally uses UUIDs of nodes and thinks that those are unique and shareable nodes share the same uuid. So what ends up happening is that selecting/deselecting one of the shared nodes, acts "funny" eg. both are shown selected but deselecting only removes one of the nodes selection (visually). Actions can be done only to the "first" one. Although I think this would be fine as they are effectively the same node.
So my thinking at this point is that this could be utilized for some special use cases but also should be avoided because of the admin UI quirks.
BR, Samuli