Andreas Schaefer created SLING-3414:
---------------------------------------
Summary: Mutlitenancy Support Integration
Key: SLING-3414
URL: https://issues.apache.org/jira/browse/SLING-3414
Project: Sling
Issue Type: Improvement
Components: API, Engine
Affects Versions: Servlets Resolver 2.3.2, Engine 2.2.12, API 2.5.2,
Resource Resolver 1.1.0
Reporter: Andreas Schaefer
Based on the proposal for the multi-tenancy integration:
https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support+Integration
this is the issue to track it.
The Tenant module (contrib/extension/tenant) is just the data structure and
Felix UI to handle Tenants but it does not provide any functionality to
actually enable multi-tenancy in Sling.
As described in the original proposal
https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support there
must be support for a per-call enhancement of the Search Path in order to
prepend the Search Path with the Tenant specific search path. This needs to be
done in the Resource's Resource Path but also in the Servlet Resolver which
uses the Administrative Resource Resolver and so need to change its Search Path
on a per-call basis. Finally the Servlet Resolver needs to change its Caching
mechanisms to let Servlets being cache per tenant (if on the tenant search
path) in order to provide a tenant specific view.
Because the tenant can be identified by different means like subdomains, path,
cookies, parameters etc the Tenant module cannot provide a catch-all
implementation. Therefore sling should provide a Service interface for the
client to implement on how to obtain a tenant id.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
