[NETCONF-921] Separate out LockChangeListener from NetconfDeviceSalFacade Created: 06/Dec/22 Updated: 01/Jan/23 Resolved: 01/Jan/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Improvement | 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: |
|
||||||||||||
| Description |
|
LockChangeListener maintains a single boolean in NetconfDeviceDataBroker and AbstractNetconfDataTreeService. This drives the behaviour of NetconfDataTreeService and NetconfDeviceDataBroker transactions. Unfortunately, this implies sal-netconf-connector has a strong tie with netconf topology – which is not appropriate. Split the logic of maintaining this bit into netconf.topology.spi while enforcement remains in sal-netconf-connector – providing another step in making sal-netconf-connector topology-independent. |