Uploaded image for project: 'mdsal'
  1. mdsal
  2. MDSAL-392

Clean up BindingRuntimeContext instantiation

    XMLWordPrintable

Details

    • Epic
    • Status: Resolved
    • Medium
    • Resolution: Done
    • None
    • 6.0.0
    • Binding runtime
    • None

    Description

      DOM OSGi SchemaContext services and the interaction between binding codec, adapter are quite a bit perplexing. The wiring should really be simplified, so that we can arrive at a place where the codec tree is completely predictable and does not rely on TCCL.

      One key ingredient we seem to be missing is that the set of ClassLoaders from which a particular SchemaContext should be carried with it.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. CONTROLLER-1882 Inject DataBroker only when all shards have leaders

          • Medium - Has the potential to affect progress.
          • Resolved

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MDSAL-525 Eliminate blueprint from mdsal-binding-dom-adapter

          • Medium - Has the potential to affect progress.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDSAL-250 Eliminate duplicate YangTextSchemaContextResolvers

          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. MDSAL-235 [INFO] Failed to fully assemble schema context for [...]

          • Resolved

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDSAL-520 Replace blueprint containers with OSGi DS components

          • Medium - Has the potential to affect progress.
          • Confirmed
          # Subject Branch Project Status CR V
          79999,2 significant clean up in mdsal-binding-dom-codec-osgi master mdsal Status: ABANDONED -1 +1
          87092,22 Bump yangtools to 5.0.0-SNAPSHOT master mdsal Status: MERGED +2 +1
          87828,25 Promote BindingRuntimeContext to binding-generator-api master mdsal Status: MERGED +2 +1
          87829,9 Move BindingSchemaContextUtils.findInstantiatedCase() master mdsal Status: MERGED +2 +1
          87830,9 Promote AbstractBaseType to binding.model.api master mdsal Status: MERGED +2 +1
          87831,9 Deprecate BindingRuntimeContext.getEnumMapping() master mdsal Status: MERGED +2 +1
          87832,10 Remove BindingRuntimeContext.getEnumMapping() master mdsal Status: MERGED +2 +1
          87853,13 Promote ReferencedTypeImpl to model.api.DefaultType master mdsal Status: MERGED +2 +1
          87854,20 Promote codec exceptions to binding.codec.api master mdsal Status: MERGED +2 +1
          87859,11 Refactor GeneratedClassLoadingStrategy master mdsal Status: MERGED +2 +1
          87860,16 Move mdsal-binding-dom-codec tests master mdsal Status: MERGED +2 +1
          87865,3 Make Binding(Runtime)Generator a proper service master mdsal Status: MERGED +2 +1
          87867,2 Make sure docs depend on codec-api master mdsal Status: MERGED +2 +1
          87872,1 YangSchemaUtils is not used anywhere, remove it master mdsal Status: MERGED +2 +1
          87873,3 Rehost BaseYangTypes master mdsal Status: MERGED +2 +1
          87874,1 Remove BindingDataAware master mdsal Status: MERGED +2 +1
          87875,2 Separate out mdsal-binding-dom-codec-spi master mdsal Status: MERGED +2 +1
          87876,2 Deprecate AugmentationReader for removal master mdsal Status: MERGED +2 +1
          87877,2 Remove AugmentationReader master mdsal Status: MERGED +2 +1
          87899,1 Deprecate AugmentationReader for removal 5.0.x mdsal Status: MERGED +2 +1
          87900,1 Deprecate BindingRuntimeContext.getEnumMapping() 5.0.x mdsal Status: MERGED +2 +1
          87901,1 Refactor GeneratedClassLoadingStrategy 5.0.x mdsal Status: MERGED +2 +1
          87902,1 Refactor GeneratedClassLoadingStrategy v4.0.x mdsal Status: MERGED +2 +1
          87903,1 Deprecate BindingRuntimeContext.getEnumMapping() v4.0.x mdsal Status: MERGED +2 +1
          87909,5 Split out mdsal-binding-runtime-{api,spi} master mdsal Status: MERGED +2 +1
          87911,2 Specialize ModuleInfoBackedContext for no fallback master mdsal Status: MERGED +2 +1
          87914,1 Remove BindingSchemaContextUtils master mdsal Status: MERGED +2 +1
          87915,1 runtime-api does not depend on spec-util master mdsal Status: MERGED +2 +1
          87916,8 Use OSGi DS instead of Activator/blueprint master mdsal Status: MERGED +2 +1
          87927,4 Split up BindingRuntimeContext master mdsal Status: MERGED +2 +1
          88017,2 Remove BindingRuntimeContext{Listener,Service} master mdsal Status: MERGED +2 +1
          88027,2 Use only BundleContext in BindingClassLoadingStrategy master mdsal Status: MERGED +2 +1
          88028,18 Rework binding component instantiation master mdsal Status: MERGED +2 +1
          88038,2 Split off DefaultBindingCodecTreeFactory master mdsal Status: MERGED +2 +1
          88039,1 Untangle BindingCodecContext/BindingNormalizedNodeCodecRegistry master mdsal Status: MERGED +2 +1
          88043,1 Use BindingCodecTreeFactory in yanglib master mdsal Status: MERGED +2 +1
          88129,1 Fix minor typos from previous patches master mdsal Status: MERGED +2 +1
          88131,1 Make OSGiModuleInfoSnapshot generation unsigned master mdsal Status: MERGED +2 +1
          89297,2 OSGiDOMSchemaService should provide YANG sources master mdsal Status: MERGED +2 +1

          Activity

            People

              rovarga Robert Varga
              rovarga Robert Varga
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: