[
https://issues.apache.org/jira/browse/SLING-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608853#comment-15608853
]
Carsten Ziegeler commented on SLING-5750:
-----------------------------------------
I'm not against considerent a dynamic search path - but script resolution is
only one part. There are different caches and other things that currently
register themselves as listeners for the search path. If now the search path is
dynamic we have to rethink everything. I'm not saying we shouldn't look into,
just trying to raise the fact that this is way more difficult than it might
look in the beginning and we have to look at the whole stack, existing
contracts etc.
> 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
> 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)
