Details
-
Epic
-
Status: Confirmed
-
Medium
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
Eliminate use of blueprint
Description
Blueprint does not observe OSGi lifecycle, opting for blocking when a service disappears. This is utterly wrong from our perspective, as we want our components to react to service lifecycle.
Replace all blueprint containers with their OSGi DS Component counterparts.
Attachments
Issue Links
- relates to
-
MDSAL-392 Clean up BindingRuntimeContext instantiation
-
- Resolved
-
-
CONTROLLER-1882 Inject DataBroker only when all shards have leaders
-
- Resolved
-
-
MDSAL-418 Wiring classes for mdsal
-
- Resolved
-