[
https://issues.apache.org/jira/browse/SLING-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614863#comment-15614863
]
Feike Visser commented on SLING-5750:
-------------------------------------
I am nicely progressing via the ResourceDecorator route.
So far the caching for the scripts we need to have another look at
> Dynamic search path to load dynamically different component renditions
> ----------------------------------------------------------------------
>
> Key: SLING-5750
> URL: https://issues.apache.org/jira/browse/SLING-5750
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Reporter: Feike Visser
>
> In the current setup in Sling there is 1:1 relation between a component and
> the code that implements this components.
> In a multi-tenant/multi-brand environment you have a need to switch this
> dynamically based on the tenant that you are in.
> Example
> [default]
> Component A -> /apps/components/componeneta/componeneta.html
> [Tenant A]
> Component A -> /apps/tenanta/componeneta.html
> [Tenant B]
> Component A -> /apps/tenantb/componeneta.html
> Content structure
> /tenanta/
> sling:scriptFolder -> /apps/tenanta
> /tenantb/
> sling:scriptFolder -> /apps/tenantb
> Suggestion: If we would implement a dynamic search path the implementation
> can choose itself where to point to when we are in a multi-tenant environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
