Hi,

same needs here (disclaimer: I also work for Adobe, but I have seen the need in 
different areas than Justin).

Let me extend on the use case: not only disabling should be possible, but also 
enabling.

Imagine a multi-cardinality service reference and the deployer wants to pick 
which services are enabled and which are not. The component provider might make 
them all off by default and the deployer opts-in individually or vice-versa 
(Justin's case of disabling something that's enabled by default). Or the ootb 
config provided by the component/application provider enables XY, but not Z, 
and the deployer wants to override that to enable YZ but not X.

Cheers,
Alexander Klimetschek
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to