[
https://issues.apache.org/jira/browse/SLING-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609656#comment-15609656
]
Carsten Ziegeler commented on SLING-5750:
-----------------------------------------
It's org.apache.sling.api.resource.ResourceDecorator - that service is called
for every *resource* resolution including script resolution
The method you implement gives you the real resource, you can check the path of
the resource or the resource type, check the request resource resolver and then
return a decorated resource - or the same
> 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)
