Re: [equinox-dev] bundle starting twice

["Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>]

I was preparing a detailed bug report, when I noticed that I do have a
non-framework import, namely org.osgi.service.event. Didn't realize
that this was a separate bundle before. If I add this to the initial
bundles set, my problem disappears.

Sorry for the false alarm.

Tom

On Mon, Jan 5, 2009 at 9:51 PM, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
> Are you updating the loginscreen bundle when you see the bundle get started
> twice or do you have multiple versions of the loginscreen bundle? If a new
> version of the loginscreen bundle is being provisioned then this is expected
> behavior. I would have expected the loginsreen bundle to bring down the
> first login screen when it is stopped and then a new loginscreen be
> displayed when it is started again.
>
> If you are not updating the loginscreen bundle and you are sure you do not
> depend on anything outside of the OSGi Framework then this is unexpected. If
> that is the case, can you open a bug against Equinox->Framework and provide
> a testcase to reproduce?
>
> Tom
>
>
>
> "Tom Huybrechts" ---01/05/2009 02:38:13 PM---Hi all,
>
>
> From:
> "Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
> To:
> "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
> Date:
> 01/05/2009 02:38 PM
> Subject:
> [equinox-dev] bundle starting twice
> ________________________________
>
>
> Hi all,
>
> I have a client application in which I added a bundle ('loginscreen')
> at start level 1 to display a login screen.
> While this screen is presented to the user, the framework startup
> continues as usually, with org.eclipse.update.configurator at level 3.
> Now when modifications have occurred to the set of available bundles,
> Package Admin will always stop my loginscreen bundle, and restart it.
> In this case that means there will be two login screens...
>
> The loginscreen bundle only depends on the framework, and no other
> bundles depend on it, so I don't see why it would need to be
> restarted.
>
> Can I avoid this behaviour somehow ? I don't want to start the bundle
> after org.eclipse.update.configurator.
>
> Tom
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>