Re: [I] The dependency manager implementation uses bundle context of other bundles (celix)
PengZheng closed issue #561: The dependency manager implementation uses bundle context of other bundles URL: https://github.com/apache/celix/issues/561 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] The dependency manager implementation uses bundle context of other bundles (celix)
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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] The dependency manager implementation uses bundle context of other bundles (celix)
PengZheng commented on issue #561: URL: https://github.com/apache/celix/issues/561#issuecomment-1560624197 Or we can fix `celix_framework_useBundle` with `onlyActive == true`. Maybe we could solve #557 and this one together. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
