[CONTROLLER-196] Remove bundlecontext usage from services managed by config-subsystem Created: 06/Mar/14 Updated: 25/Jul/23 Due: 30/Jun/14 Resolved: 03/Jul/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Tomas Olvecky | Assignee: | Tony Tkacik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
RuntimeMappingModuleFactory, SchemServiceImplSingletonModuleFactory and maybe others are passing bundlecontext around. That should be avoided. |
| Comments |
| Comment by Tony Tkacik [ 30/Jun/14 ] |
|
Potential offenders Binding-Aware broker: Reason: DOM Broker registers bundleContext for registration ./sal-binding-broker/src/main/java/org/opendaylight/controller/config/yang/md/sal/binding/impl/BindingAsyncDataBrokerImplModuleFactory.java DOMBroker: DOM Broker requires BundleContext for Extender / Publishing services |
| Comment by Tony Tkacik [ 30/Jun/14 ] |
|
Removed requirement for BundleContext for most of services. https://git.opendaylight.org/gerrit/#/c/8462 Only two left-out are: SchemaServiceImplSingletonModule - which is OSGI extender and requires BundleContext in order to work properly RuntimeMappingModule - which is OSGI extender and must be singleton per JVM and may be instiantiated also by config-manager. |