Hi Stefan, On Fri, Aug 22, 2014 at 2:03 PM, Stefan Seifert <[email protected]> wrote: >>System content: >>Defines how a specific version of the system behaves. >>Multiple system versions can coexist in a shared content repository >>(as we demonstrated in [1], in a limited way) > > this is for example configuration - but as you describe it mainly > system-level configuration (e.g. OSGI configuration). > what is with the other types of configuration on the different levels > (regions, tenants, sites). they do not belong into the role "system content", > but they do not fit in the other roles as well...
I agree, that content might be called "tenant-specific application content" maybe? ... >>Application content: >>Extensions or overrides of system content, that modify how the system >>behaves. >>Usually tenant-specific, or maybe shared between a group of tenants ... > i assume the whole application bundle falls into this category? but an > application bundle usually > consist of both OSGi bundles (system role) and scripts (application context > role).... Currently I don't think we have a way to make OSGI services specific to a tenant, unless the method signatures require tenant information. This is a whole topic in itself. -Bertrand
