-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove service_tracker.h service_tracker_customizer.h header and bundleContext_getServiceReference #87
Comments
As discussed in https://lists.apache.org/thread/6gp5crw1pp408jw2fbwlg149n5rm36pv before the service tracker headers can be removed from the public API some additional tracker API in the bundle context is needed. Mainly to be able to use tracked services out side of the celix event thread. |
Also update the celix_bundleContext_trackServices usage.
Also: - Remove celix_bundleContext_trackService and celix_bundleContext_trackServiceAsync functions. - Update doxygen for useTrackedService* calls. - Remove celix_bundle_destroyServiceTrackerList. function by return an array list with a configured remove callback. - Remove waitTimeoutInSeconds option for celix_tracked_service_use_options_t.
With the addition of
|
Fix race condition in `celix_bundleContext_getDependencyManager` and avoid write lock when possible.
… fix possible nullptr dereference.
1. Use acquire-release pair to synchronize the service user with the service stopper. 2. Reduce CPU usage when waiting for service user. 3. Fix gcc -Wstringop-truncation warning.
Note that also means that useService* functions and methods are no longer use-able in the Celix event thread.
Simplified the implementation of |
The service_tracker.h and service_tracker_custimizer.h should be removed. Service tracker should be control-able from the bundle context (see CELIX-441)
Also remove the bundleContext_getServiceReference(s) this should also been unnecessary because of CEILX-441.
This make to total Celix API smaller
Original creation date: 10/Apr/2018
Reporter: @pnoltes
The text was updated successfully, but these errors were encountered: