Re: [osgi-dev] Declarative disabling of a DS component

2016-02-16 Thread Alexander Klimetschek
On 16.02.2016, at 13:03, BJ Hargrave wrote: > A component must be first be enabled which requires it to live in a bundle > which is started and also to have the component description enabled (either > via the declaration or the API). [X] > An enabled component must then

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-16 Thread BJ Hargrave
I do not see a mix of concerns here. There is component enablement and there is component satisfaction.   A component must be first be enabled which requires it to live in a bundle which is started and also to have the component description enabled (either via the declaration or the API).   An

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-16 Thread Alexander Klimetschek
It would also be interesting if this was previously discussed and if yes, what arguments spoke against it (our resident osgi experts mentioned this might have been a topic before). Thanks, Alex > On 15.02.2016, at 08:22, Christian Schneider wrote: > > Yes .. it is a

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-15 Thread Christian Schneider
Yes .. it is a bit of a mix of concerns but as far as I know it is the only option at the moment. Christian On 15.02.2016 17:13, Justin Edelson wrote: Hi Christian, Per my original email, there are some limitations of the require policy. Further it seems to me that this is a bit of a mix of

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-15 Thread Justin Edelson
ing the components that should or should not be enabled. >> >> -- >> >> BJ Hargrave >> Senior Technical Staff Member, IBM // office: +1 386 848 1781 >> OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 >> hargr...@us.ibm.com >> >> >

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-15 Thread Justin Edelson
lliance // mobile: +1 386 848 3788 > hargr...@us.ibm.com > > > > - Original message - > From: Justin Edelson <jus...@justinedelson.com> > Sent by: osgi-dev-boun...@mail.osgi.org > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Cc: > Subjec

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-15 Thread Christian Schneider
You can not easily disable components. You can do it the other way round though by using the configurationPolicy REQUIRE. If you specify that the component needs a mandatory config then it will only be enabled if the config exists. So the deployer can use the existence of configs to enable /

Re: [osgi-dev] Declarative disabling of a DS component

2016-02-15 Thread BJ Hargrave
DS is already declarative. What additional declarations are you thinking of? Where would a "deployment' declaration come from? If the deployment declaration disabled a component, how would the component later become enabled? Through API calls? How would the deployer create and deploy deployment

[osgi-dev] Declarative disabling of a DS component

2016-02-11 Thread Justin Edelson
Hi, I see a real need in the DS specification for a standardized way to declaratively disable DS components by default *at deploy time* whereas the current model (please correct me if I'm wrong) only allows for components to be disabled by default at packaging time. The primary use case I'm