|Re: Shutting down the OSGi framework [message #935780 is a reply to message #895816]
||Sun, 07 October 2012 10:01
| Karl Weber
Registered: September 2010
O.k. I think I understand my problem a little bit better, but I don't have a solution.|
I start the framework with the options
The first option ensures, that no application is started automatically. This works, the main thread is indeed waiting and I have to launch my application manually.
The second option ensures, that Quote:
the main thread will continue to wait for another application descriptor to be launched after the currently running application has quit. Stopping the system.bundle (i.e. the bundle with a bundle ID equel to zero) will force the main thread to stop waiting for another application to launch
This, however, does not work. The main thread keeps on waiting forever after the first application stopped and I called
The only proof I have is that once I set this option to false, everything works, i.e. the main thread stops after the first application quit, and the framework stops after calling
Unfortunately this will prevent me from launching another application after my first application quit.
My current understanding is, that this is a bug, or am I missing something else?
Powered by FUDForum
. Page generated in 0.02000 seconds