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 components to be “responsive”. As requirements changed the new responsive content also had to be re-authored. But while not all pages exist yet under responsive tree we have to be able to render old content using legacy components. And yes we could still run some scripts to change resource types under responsive tree. But eventually we will throw away old components and would like to keep the project structure the same (main reason for the same resource types). So, we would need to run scripts again to change resource types back. I just found patching servlet resolver easer. It has worked well for us and we can just throw it away later. The only issue like I said is upgrading. This was intended as temp solution until we migrate the site completely. But content re-authoring is taking longer than originally assumed and we have to keep supporting both responsive and legacy content.
I can still re-patch newer servlet resolver when we need to upgrade. It’s not a huge problem. But I wanted to look into implementing something more general that I could give back open source community and Tenant API seemed ideal. Henry > On Mar 2, 2016, at 12:53 AM, Jörg Hoh <jhoh...@googlemail.com> wrote: > > 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 <hsaginor.apa...@gmail.com>: > >> 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
