From: Richard S. H. <he...@un...> - 2004-06-02 11:07:48
|
Manuel Santillan Palencia wrote: >However, the thing is that the system hangs, even the tui, so you must >kill oscar. But if I extract the code and put it inside a BundleListener >which checks that the bundle event corresponds to BundleB.STARTED, then >it works fine. If I find a bit of time, I shall try to recreate it, for >the moment I have not been able... > > If you can find the time to recreate it, I would definitely like to take a look at it. >When a started bundle is updated it is restarted. Then when packages are >refreshed, it is restarted with the new code. > > Correct. >If a bundle is started, and then you change the platform start level to >be higher than its startlevel, it stops. If you update the bundle and >refresh and change again the platform start level to be lower than the >bundle level, it is not started. Should not the service remember which >bundles were in started state for a given startlevel even if they are >updated? > > It sounds like you reversed this, I assume you mean "change the platform start level to be lower than its start level..." Or do you mean change the bundle start level to be higher? At any rate, which version of Oscar are you using? I think this was a bug that was corrected in the latest betas, so just wait for 1.0.0 to be released and your problem should be solved. Speaking of 1.0.0, what version of Oscar were you getting your deadlock against? Perhaps I could convince you to do some testing on the 1.0.0 beta if you are not already doing so... -> richard |