In words:
- the base is a Service which provides a Netconfnode-state-API by using a netconf-change-listener
- on top of this service several devicemanagers which can register a callback function for a connected netconfnode
- the devicemanager can then decide if it wants to keep the netconfsession (based on capabilities) and register a notification listener on this or it wants to ignore it
- the notification-service provides the messages for the websevice cluster, so that GUI clients can be informed about changes
- these messages are:
- mountpoint created
- mountpoint deleted
- ProblemNotification
- AttributeValueChangedNotification
- data-provider has to register on netconfnode-state-API for filling tables:
- network-element-connection
- faultlog
- faultcurrent
- maintenancemode