On Monday 07 November 2016 11:35:19 Bertrand Delacretaz wrote: > On Mon, Nov 7, 2016 at 11:20 AM, Oliver Lietz <[email protected]> wrote: > > ...If a bundle requires a capability the system has to provide that > > capability otherwise the bundle would not resolve.... > > That's a nice model but IIUC Carsten earlier in this thread OSGi > capabilities cannot be created at runtime so that won't work for > service users or access rights.
You can remove the resource which provides the capabilities from the runtime and readd it with altered capabilities (which obviously leads to oscillating systems). But I don't think it makes sense to use Requirements/Capabilities for system users and ACLs. > If we want to express the access requirements of bundles or services > in a self-explaining way we could use the repoinit syntax (maybe > tweaked to be more declarative) and implement a service that checks > whether those expectations are met. Yes... and a service which executes repoinit statements at runtime (not sure if Carsten already created an issue for that). O. > Having a way to verify the conformance of a Sling instance with a set > of repoinit statements would be useful anyway - but that's not > implemented so far. > > -Bertrand
