JochenHiller commented on PR #190:
URL: https://github.com/apache/felix-dev/pull/190#issuecomment-1355040043
@karlpauls @cziegeler I added now a proposal for a fix of the test case.
From my point of view there are two problems happening:
1. When a bundle start level will be changed from a bundle activator which
is started by FrameworkStartLevel thread, the way to process that is by default
asynchronous. Which does not work when bundle startup is already done by
FrameworkStartLevel thread, so the processing has to be done in current thread
synchronous by calling `m_felix-setBundleStartLevel()` on Felix framework
2. When this method `m_felix-setBundleStartLevel()` will be called, there is
already a computed TreeMap of `m_startLevelBundles` in Felix. This list
contains the bundle with old start level. So new start level requested needs to
be updated by removing old tuple and adding new tuple to get it in right
sort-order in TreeMap.
I found that by adding a huge number of debug messages. I will leave them in
for your testing. If you would agree on change, I would remove all debug output
again, and do some re-formatting of code to Felix code style.
My tests are running fine, also the whole Felix framework tests did also
work well.
Do you consider to re-run OSGi TCK test suite for a complete test? I can
offer to support on that as well if helpful.
--
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-unsubscr...@felix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
