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 renderings.
Jörg 2016-03-01 23:06 GMT+01:00 Henry Saginor <[email protected]>: > 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 > implemented via multi tenancy. > But I don’t think this has been integrated into script resolution process > yet. What is the current state of this and what’s the plan? > > I can work on a patch. But I would need some guidance to make sure it is > constant with the Sling vision for multitenancy. > > Are there any other ideas on how to do this? Currently my application has > a customized Servlet Resolver that does this. > But this makes upgrades more difficult because application code is coupled > with a specific version of servlet resolver. So, we have to port our code > every time we need to upgrade Servlet Resolver. > > [1] https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support > [2] > https://cwiki.apache.org/confluence/display/SLING/Multitenancy+scenarios+and+use+cases > < > https://cwiki.apache.org/confluence/display/SLING/Multitenancy+scenarios+and+use+cases > > > > Regards, > > Henry -- Cheers, Jörg Hoh, http://cqdump.wordpress.com Twitter: @joerghoh
