[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637888#comment-13637888
]
Felix Meschberger commented on SLING-2710:
------------------------------------------
I think the confusing stems from the names ...
TenantProvider is used by client applications to read tenants and tenant
information.
TenantManager is used by management agents to actually manage tenants such as
creating, removing, or updating them.
There is only a single TenantProvider and only a single TenantManager in the
framework.
The idea is properly separate read-only access and management access into
separate APIs since the read-only case will be the major use case while the
update use case should be reserved to management applications, such as for
example some Tenant management UI.
> 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
