On Wed, Jul 30, 2014 at 10:13 AM, anjan <[email protected]> wrote:
> ...we want multi tenancy at the content level...

I wonder if just mounting an additional ResourceResolver on /somePath
for example would do the trick - and combine that with /etc/map
mappings so each http://tenantN.example.com maps to /somePath/tenantN
which uses its own ResourceResolver mapping to its own content
repository.

Trying that shouldn't be too hard. Not sure if and how searching would work.

-Bertrand

Reply via email to