[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637881#comment-13637881
]
Carsten Ziegeler commented on SLING-2710:
-----------------------------------------
I had a brief look at the current state and I think there is something wrong
wrt TenantProvider/TenantManager. While the API of TenantProvider suggests that
there is more than a single provider, the implementation uses exactly one,
which is also the manager implementation. So either we separate this, or remove
the tenant provider interface.
Right now, I would opt for removing TenantProvider, especially as this opens
some questions when creating a new tenant through the manager. Which provider
is used and why and wouldn't we need a way to create a tenant based on a
provider?
> Define TenantManager API
> ------------------------
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Tenant 1.0
>
> Attachments: SLING-2710-2.patch, SLING-2710.patch
>
>
> Tenants currently can only be administered (create, update, remove) through
> the Web Console. In addition the TenantProvider service interface allows for
> looking tenants up (read).
> For administrative purposes it would be good to have a TenantManager service
> interface which allows for these administrative tasks. Something like:
> public interface TenantManager extends TenantProvider {
> Tenant create(String tenantId, Map<String, Object> properties);
> void setProperty(Tenant tenant, String name, Object value);
> void remove(Tenant tenant);
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
