Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
SLING-4386 Multi-tenant content model prototype
- Resolved