Hi Yes, it indeed sounds interesting, but I have two concerns (big ones ? not sure):
1. it uses Felix DependencyManager. Not a big deal, just an additional bundle 2. OSGi Platform services have to be adapted as well. Particularly nasty probably are things like SCR and Blueprint which manage objects on behalf of bundles and must thus be knowledgeable of that situation maybe also by virtue of the MultieTenantActivator and the BundleContext wrappers. Regards Felix Am 30.08.2014 um 05:14 schrieb Alexander Klimetschek <aklim...@adobe.com>: > On 28.08.2014, at 16:19, Ben Fortuna <benfort...@gmail.com> wrote: > >> The amdatu project may also be useful for multi-tenancy at the bundle >> level. I haven't used it personally but it looks interesting: >> >> http://amdatu.bitbucket.org/components/multitenancy.html > > Interesting! They actually allow running separate bundles for separate > tenants and isolating them from each other. It definitely sounds like a good > solution when you have different tenants licensing different "apps" and you > want to shield them. > > The page above also talks about the separation between tenant and platform > services - many services are better served global (example a logging service) > and a first question is to identify what you would run as platform and what > per tenant. It might also be a matter of performance - running many bundles > per tenant might not be the best idea (don't know) and if you can handle the > multi-tenancy within a shared bundle easily that would be less resource > consuming. > > Cheers, > Alex >
