[
https://issues.apache.org/jira/browse/SLING-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614763#comment-15614763
]
Vineet Kumar edited comment on SLING-5750 at 10/28/16 8:36 AM:
---------------------------------------------------------------
While I agree that this is a big fix, I do believe that this will be a great
enhancement to Sling. The way I look at it, is that component and its
script/views are tightly coupled based on the component folder. Decoupling
among them will open huge opportunity. What if component define its own search
order for its scripts/views and also expose a hook for custom extension of
search paths? That way a single component will be able to suffice multiple
brands easily and a very good feature from content migration point of view.
What does group feel?
was (Author: vineet.kumar):
While I agree that this is a big fix, I do believe that this will be a great
enhancement to Sling. They way I look at it is that component and its
script/views are tightly coupled based on the component folder. Decoupling
among them will open huge opportunity. What if component define its own search
order for its scripts/views and also expose a hook for custom extension of
search paths? That way a single component will be able to suffice multiple
brands easily and a very good feature from content migration point of view.
What does group feel?
> 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)
