Details
-
Story
-
Status: Resolved
-
Medium
-
Resolution: Done
-
None
-
None
Description
mdsal-binding-dom-adapter has remnants of its tight integration with mdsal-binding-dom-codec in the form of its blueprint container. This container
- listens on DOMSchemaService
- maintains a BindingToNormalizedNodeCodec, which internally maintains a BindingRuntimeContext (and BindingCodecContext)
- publishes it to OSGi registry as org.opendaylight.mdsal.binding.dom.codec.api.BindingNormalizedNodeSerializer
- uses it as reference for published org.opendaylight.mdsal.binding.dom.adapter.spi.AdapterFactory
Note some of these interactions work on the exact class, so we need to untangle what is actually going on.
Attachments
Issue Links
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 82671,7 | Switch mdsal-binding-dom-adapter to Declarative Services | master | mdsal | Status: ABANDONED | 0 | -1 |
| 88160,4 | Expose BindingInstanceIdentifierCodec from BindingCodecTree | master | mdsal | Status: MERGED | +2 | +1 |
| 88166,3 | Reduce BindingNormalizedNodeCodecRegistry proliferation | master | mdsal | Status: MERGED | +2 | +1 |
| 88204,12 | Refactor OSGi ModuleInfoSnapshot/BindingRuntimeContext | master | mdsal | Status: MERGED | +2 | +1 |
| 93343,1 | Expose BindingInstanceIdentifierCodec from BindingCodecTree | 5.0.x | mdsal | Status: MERGED | +2 | +1 |