2012/11/28 Bertrand Delacretaz <[email protected]> > On Wed, Nov 28, 2012 at 4:09 PM, Adrian Gschwend <[email protected]> > wrote: > > ...- which is related to the reason why Reto adds it: In professional > > environments we need multi-tenancy, for having more than one tenant you > > need some kind of security... > > That's *your* use case - as I explained mine differs. > > Multi-tenant Stanbol looks to me like a different product than the > plain stateless engine that I and others consider, in which case a > separate launcher might be more appropriate for the multi tenant > variant, with a slightly different set of bundles and configs that > enables security by default. >
Bertrand was faster than myself - so I just have to agree with him. What about creating another launcher configuration that has has security enabled by default? Enabling something in Stanbol means that it is in some launcher configuration. We are used to call the full-launcher the default one but it was never defined to be something like default. We could also have another Jenkins instance that could execute integration tests against other launchers if we think it is necessary. Best, - Fabian -- Fabian http://twitter.com/fctwitt
