[MDSAL-525] Eliminate blueprint from mdsal-binding-dom-adapter Created: 29/Feb/20  Updated: 16/Apr/20  Resolved: 16/Apr/20

Status: Resolved
Project: mdsal
Component/s: Binding runtime
Affects Version/s: None
Fix Version/s: 6.0.0

Type: Story Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by MDSAL-392 Clean up BindingRuntimeContext instan... Resolved
Relates
relates to MDSAL-526 Disconnect ValueTypeCodec from Illega... Confirmed
Epic Link: Eliminate use of blueprint

 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.

 Comments   
Comment by Robert Varga [ 16/Apr/20 ]

Fixed in https://git.opendaylight.org/gerrit/c/mdsal/+/89040

Generated at Wed Feb 07 20:10:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.