Hi

> Am 09.12.2014 um 03:02 schrieb Richard Hall <[email protected]>:
> 
> On 12/8/14 20:47 , Benson Margulies wrote:
>> On Mon, Dec 8, 2014 at 8:34 PM, Richard S. Hall <[email protected]> wrote:
>>> On 12/8/14 18:07 , Benson Margulies wrote:
>>>> FrameworkStartLevel#setStartLevel takes listeners, which looks really
>>>> useful. Can I call it instead of Framework#start?
>>> 
>>> They don't do the same thing, but certainly you can use either...
>> 
>> That's what I'm trying to sort out. To be perfectly clear about my
>> ignorance, I don't understand what the FrameworkStartLevel method is
>> for if it's not another way to express the Framework method.
>> 
>> Here's what I have working:
>> 
>> 1. framework.init();
>> 2. obtain default bundle start level from FrameworkStartLevel
>> 3. installBundle all bundles
>> 4. set start level for each bundle by adapting to a BundleStartLevel
>> 5. start all bundles
>> 6. framework.start
>> 
>> So, where would FrameworkStartLevel#setStartLevel fit into all this?
>> Is it only useful if I need to change the start level after
>> framework.start()?
> 
> Yeah, it is pretty much only useful after you activate the framework (i.e., 
> call start()). Although, after a quick look, I'm not 100% certain what the 
> Felix framework implementation will do if you call setStartLevel() before 
> calling start()…

My interpretation is, that the init() method sets the StartLevel service up and 
then calling setStartLevel instead of Framework.start() would probably start 
the framework except: The framework STARTED event would not be sent !

It would really stick to the original intent, as I read it: Use 
Framework.start() to start the framework and use 
FrameworkStartLevel.setStartLevel to change the current start level.

Regards
Felix

> 
> -> richard
> 
>> 
>> 
>> 
>> 
>> 
>>> 
>>> -> richard
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

Reply via email to