Re: searchPath based on content path + multitenancy

Bertrand Delacretaz wrote > On Thu, Mar 3, 2016 at 8:26 AM, Carsten Ziegeler wrote: >> ...I was thinking of rewriting the whole script resolution mechanism to >> have a better caching mechanism. Maybe if we do one of these things we >> look into the other as well :).. > > I

Re: searchPath based on content path + multitenancy

On Thu, Mar 3, 2016 at 8:26 AM, Carsten Ziegeler wrote: > ...I was thinking of rewriting the whole script resolution mechanism to > have a better caching mechanism. Maybe if we do one of these things we > look into the other as well :).. I think so - including some form of

Re: searchPath based on content path + multitenancy

Henry Saginor wrote > Thanks Bertrand, > I see that at Sling engine level ServletResolver is pluggable already. So, > this is something I could do at the project level as well. > Project level ServletResolver could still delegate to default > SlingServletResolver, I suppose, after resolving

Re: searchPath based on content path + multitenancy

Thanks Bertrand, I see that at Sling engine level ServletResolver is pluggable already. So, this is something I could do at the project level as well. Project level ServletResolver could still delegate to default SlingServletResolver, I suppose, after resolving script name to absolute path or

Re: searchPath based on content path + multitenancy

Hi Jorg, Thank you for your input. I have considered using different resource types. This would work. But my use case is a bit different from true multi-tenancy. This is one company/tenant hosting their own Sling (CQ just upgraded to AEM 6.1) instances. They have been working on reimplementing

Re: searchPath based on content path + multitenancy

Hi, On Tue, Mar 1, 2016 at 11:06 PM, Henry Saginor wrote: > ...Currently my application has a customized Servlet Resolver that does > this... If you're adventurous you could have a look at my content-based dynamic search path prototype at [1], that does something

Re: searchPath based on content path + multitenancy

Hi Henry, we had the same challenge, and instead of changing/patching the resource resolver we change the resource types. So each tenant has its own resourcetype namespace; for example /apps/tenannts/components/page/homepage. So we can use the "defaults" here, and just provide different

searchPath based on content path + multitenancy

Hi, I have a need to execute different scripts for my resource types based on content resource path. For example resources under /content/abc and /content/xyz have the same resource types but should be rendered differently. I was reading [1] and [2] which seem to describe how this can be