pnoltes commented on issue #561: URL: https://github.com/apache/celix/issues/561#issuecomment-1561687561
Good point. Maybe adding a "lifecycle" read-write lock per celix_framework_bundle_entry_t and only allow bundle lifecycle changes if you have a write lock and use a read lock when useBundle callbacks are processed. In this situation the bundle lifecycle cannot change within a use bundle callback, and only 1 bundle lifecycle change can happen per bundle. I also think that the usage of an other bundle context is not clean, but this is lower prio issue. -- 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...@celix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
