[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-2710.
Tenant 1.0 has been released, hence closing issues now.
> Define TenantManager
er.
> >> */
> >> @ProviderType
> >>
> >>
> >> >And maybe a different name than TenantProvider - I might be biased but
> >>it
> >> >sounds similar to ResourceProvider where we have a potential set of
> &
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>
der - I might be biased but
>>it
>> >sounds similar to ResourceProvider where we have a potential set of
>> >providers and not just a single one.
>>
>> I don't have too strong of an opinion regarding the name. But I think
>>the
>&
iased
>>>but it
>>> >sounds similar to ResourceProvider where we have a potential set of
>>> >providers and not just a single one.
>>>
>>> I don't have too strong of an opinion regarding the name. But I think
>>>the
>>> dist
ourceProvider where we have a potential set of
>> >providers and not just a single one.
>>
>> I don't have too strong of an opinion regarding the name. But I think the
>> distinction between the general (and broder) use of reading tenants as
>> opposed to the
the general (and broder) use of reading tenants as
> opposed to the specialized management of tenants warrants having two
> separate APIs.
>
> In any case, there is, of course, also an AdapterFactory for tenants in
> the implementation.
>
> Regards
> Felix
>
>
s in
the implementation.
Regards
Felix
>
>> Define TenantManager API
>>
>>
>> Key: SLING-2710
>> URL: https://issues.apache.org/jira/browse/SLING-2710
>> Project: Sling
>> Issu
Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>
Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>
ider 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 Tenan
n in Rev. 1451514.
Unit tests and potential fixes following.
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
>
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-2710:
Assignee: Felix Meschberger
> Define TenantManager
Hi Ruben
Am 21.02.2013 um 16:47 schrieb Ruben Reusser:
>
> i was wondering if tenants should work differently and be more transparent to
> the user by allowing to swotch the osgi properties per tenant. this would
> allow for a more transparent implementation without forcing the developer to
>
Hi,
2013/2/21 Felix Meschberger
> Hi
>
> SLING-2710 [1] proposes the addition of a TenantManager service interface.
> Thanks for the comments so far.
>
> One question that came up in the issue is whether the TenantManager should
> extend the TenantProvider or not.
>
> I am a bit undecided: On th
i was wondering if tenants should work differently and be more transparent to
the user by allowing to swotch the osgi properties per tenant. this would allow
for a more transparent implementation without forcing the developer to think
about tenants that much.
Ruben
On Feb 21, 2013, at 2:14 AM
Hi
SLING-2710 [1] proposes the addition of a TenantManager service interface.
Thanks for the comments so far.
One question that came up in the issue is whether the TenantManager should
extend the TenantProvider or not.
I am a bit undecided: On the one hand I think that the TenantManager is not
.
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>
ffect with setProperty I agree that
from a orthogonality perspective this might make sense. How about a
removeProperties(Tentant, String...)
method ?
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https
pour moi.
Thus all good :-)
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
>
String name, Object value);
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
>
ts
(means the TenantProvider API should change as well).
Maybe you could achieve this by setting the ACL in the content referenced by
the tenant, wdyt ?
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://
e on getTenants/getTenant. Regarding addPermissions, it
is restrict role based access at tenant level (like having write access for
admins/moderators and read access for everybody else).
> Define TenantManager API
>
>
>
nant don't need to be added as it is already available
in the TenantProvider. Beside, what would be the use of
addPermissions(ACLEntry[]) ?
+1 for the proposed API and for adding removeProperty method
> Define TenantManager API
>
>
>
ArrayList getTenants
- Tenant getTenant(String)
- removeProperty(Tenant tenant, String propName)
- addPermissions (ACLEntry[]) //similarly update, delete, get Permissions.
- assuming tenant can be adapted to JCR node.
> Define TenantManager API
>
>
>
read access from create, update, delete access.
> Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
>
ra's description TenantManager extends TenantProvider interface but
in patch it doesn't.
2. No api to retrieve tenant from TenantManager. In fact TenantProvider has api
to retrieve tenant from tenantId.
> Define TenantManager API
>
>
>
Define TenantManager API
>
>
> Key: SLING-2710
> URL: https://issues.apache.org/jira/browse/SLING-2710
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Feli
[
https://issues.apache.org/jira/browse/SLING-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-2710:
-
Attachment: SLING-2710.patch
Proposed patch.
> Define TenantManager
Felix Meschberger created SLING-2710:
Summary: Define TenantManager API
Key: SLING-2710
URL: https://issues.apache.org/jira/browse/SLING-2710
Project: Sling
Issue Type: New Feature
30 matches
Mail list logo
