[NETCONF-672] Refactor SchemaRepositoryProvider into its own component Created: 24/Apr/20  Updated: 28/Apr/20  Resolved: 28/Apr/20

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: Aluminium

Type: Improvement Priority: High
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
blocks NETCONF-673 Allow sharing of common schema models... Open
blocks NETCONF-377 make netconf call home feature be clu... Confirmed
blocks NETCONF-605 Support cache refresh without restart... Confirmed

 Description   

As noted in NETCONF-671, we have had duplicate implementations of this interface. Further examination reveals this is actually left completely unused, and only the static factory is used instead.

That static factory has further problems:

  • requires static wiring
  • contains duplicate code (AbstractTopology vs. NetconfTopologyUtils)
  • all lifecycle around multiple directories is non-existent due to it being tracked in a static map only
  • there is no way to provide customized implementations

Hence this issue is about factoring the static mess out into something that has clear lifecycle and is injected into topology instances.
Generated at Wed Feb 07 20:15:36 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.