[
https://issues.apache.org/jira/browse/SLING-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4386:
---------------------------------------
Comment: was deleted
(was: At revision 1657386, (very) basic tenant-driven search paths work, for
example /content/T/example.com/about.html and
/content/T/example.com/subsite.html have the same sling:resourceType but they
are rendered by different scripts as they belong to different
ContentDrivenTenants. I have not implemented the assemblies for now, the
tenants directly define their search paths.
To minimize impact on the existing code I have just added a decision in the
SlingServletResolver to use the new MultitenantServletResolver instead, for
Resources that adapt to ContentDrivenTenant.
This would allow us to run the current Sling unchanged, while resources that
belong to a ContentDrivenTenant (defined by having an ancestor with
sling:tenantRoot property set) are processed by the new
MultitenantServletResolver. As a big part of the resolution code is factored
out of the SlingServletResolver, it shouldn't be too hard to reproduce the
functionality of the "old" SlingServletResolver in the "new"
MultitenantServletResolver while staying backwards compatible for "old"
resources.)
> Multi-tenant content model prototype
> ------------------------------------
>
> Key: SLING-4386
> URL: https://issues.apache.org/jira/browse/SLING-4386
> Project: Sling
> Issue Type: Task
> Components: General
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> I'm working on a prototype for [1], will use this issue to keep track of
> progress.
> [1]
> https://cwiki.apache.org/confluence/display/SLING/Ideas+for+a+multi-tenant+and+multi-module+content+model
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
