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 > think about tenants that much. That would be great but is not easily possible. The OSGi Configuration Admin service operates on the framework level. So configuration generally applies to the application as a whole. Of course certain configuration could be made tenant aware. For example by creating factory configuration adding a property indicating the tenant and the consumer requesting respective configuration. But we don't do that yet. For now, we have this non-intrusive Tenant Mechanism which just allows to configure and query for Tenant Information. In addition using TenantCustomizer services you may also apply further configuration upon Tenant Management, such as setting ACLs per tenant to control access to the repository on a per-tenant basis. Regards Felix > > Ruben > > On Feb 21, 2013, at 2:14 AM, Felix Meschberger <[email protected]> wrote: > >> 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 >> a TenantProvider. Also by not extending the TenantProvider the >> implementation has more freedom and it forces proper access to the service. >> >> On the other hand, for administrative tools really using the TenantManager >> having it extend the TenantProvider might make the code simpler (only one >> service to get instead of two). >> >> WDYT ? >> >> Regards >> Felix >> >> [1] https://issues.apache.org/jira/browse/SLING-2710 -- Felix Meschberger | Principal Scientist | Adobe
