[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582174#comment-13582174
]
Felix Meschberger commented on SLING-2710:
------------------------------------------
Hmm, good point. I am not sure, whether TenantManager should be a
TenantProvider or not. So at the time of creating the patch I decided it would
not be a good idea: By having two distinct interfaces we do not limit
implementations (they could be done with a single or two independent classes)
and we also clearly separate read access from create, update, delete access.
> 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
> Fix For: Tenant 1.0
>
> Attachments: 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
