karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@apache.org>
Subject Re: [DISCUSS] Remove features lifecycle in K4
Date Tue, 14 Apr 2015 08:05:02 GMT
2015-04-14 9:39 GMT+02:00 Christian Schneider <chris@die-schneider.net>:

> On 14.04.2015 09:32, Guillaume Nodet wrote:
>
>> 2015-04-14 8:52 GMT+02:00 Christian Schneider <chris@die-schneider.net>:
>>
>>  I was not aware we have this information in the wires. I will try to
>>> implement it using these.
>>>
>>> So what I would do is this:
>>> I start with the features to be stopped / started.
>>> I then propagate down to the subfeatures / bundles.
>>> For each feature processed I compute the state as the highest state of
>>> all
>>> features that depend on it and the requested state.
>>>
>>> Does that make sense?
>>>
>>>  I think that's exactly what is currently done.
>>
> I don't think so. The state to be set is computed from the highest of
> request state and current state of a feature / bundle.
> It does not take into account the states of the resources that depend on
> the resource.


The propagateState method is  recursive, so if a feature is started, a
feature that depends on it will be started, and bundles required by this
feature will be started too.



>
> Christian
>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message