[GitHub] [felix-dev] tjwatson commented on pull request #190: Fixed use case when bundle start level will be set within an bundle activator, test case FrameworkStartLevelImplTest

[GitBox <gi...@apache.org>]

tjwatson commented on PR #190:
URL: https://github.com/apache/felix-dev/pull/190#issuecomment-1355373343

   > Is that ERROR ok if we change the bundle start level during the phase to go to request framework start level?
   > It seems it does not have any implications except we get this ERROR log.
   
   I don't believe that error is OK.  In my opinion the framework should avoid logging an error in this case and move on in the processing of the rest of framework start-level changes.  But that is about it.  It sounds like the framework is acting upon a snap-shot of the bundle start-levels for the duration of the framework start-level processing.  Some bundle's start-levels may change that make it impossible to actual start the bundle at the previously determined bundle start-level snap-shot, because it has changed synchronously.
   
   From a spec perspective, I think this is fine as long as the async operation that gets queued up will stop/start the bundle according to the levels that got set during the whole framework start-level change processing.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@felix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org