Hi, On Wednesday, July 30, 2014, anjan <[email protected]> wrote:
> ...What is the > complexity (with respect to code changes) involved if the current Sling > instance has to support multiple Jackrabbit repositories?... I suspect doing that would unveil lots of subtle issues that are hidden now as we've been working with a single repository (and even single JCR workspace) all the time. Support for multiple JCR workspaces was added a while ago (you should be able to find relevant info in jira) but I'm not sure if anyone is currently using it. Another idea about multitenancy would be to have a kind of chroot functionality at the JCR repository level, where a given Sling instance would see /multi/instanceN as / at the JCR level. I have no idea how easy or hard that would be to implement at the Oak level, but if that's possible that would make such things easier. That's more questions than answers I guess - if others have concrete experience or feedback that would be welcome. -Bertrand
