[
https://issues.apache.org/jira/browse/SLING-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615631#comment-15615631
]
Justin Edelson commented on SLING-5750:
---------------------------------------
[~fvisser] I think this is a different approach than what [~cziegeler] was
recommending. He was suggesting to decorate the *content* resource with a
different resource type. Your patch decorates the script resource. Is there a
reason the former approach won't work for your use case? If you decorated the
content resource, there would be no reason for the ThreadLocal since the
resource path would contain the tenant information.
> Dynamically load 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/
> property: sling:scriptFolder -> /apps/tenanta
> /tenantb/
> property: 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)
