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.