Details
-
Task
-
Status: Resolved
-
Medium
-
Resolution: Done
-
None
Description
NetconfMessage is currently rather not nice – it very much expects to have a document, but for error handling purposes it was broken by FailedNetconfMessage.
Repair that damage by eliminating FailedNetconfMessage and instead reporting a proper failure up the stack.
While we are in the area, also move NetconfNotification to netconf-api, so we have well-known messages co-located.
As a further evolution, rename NetconfNotification to NotificationMessage and NetconfHelloMessage to HelloMessage – cutting down on verbosity.
Attachments
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 105220,4 | Remove FailedNetconfMessage | master | netconf | Status: MERGED | +2 | +1 |
| 105663,1 | Move NetconfNotification to netconf-api | master | netconf | Status: MERGED | +2 | +1 |
| 105664,1 | Hide NetconfHelloMessage.HELLO_TAG | master | netconf | Status: MERGED | +2 | +1 |
| 105665,1 | Clean up NetconfNotification constants | master | netconf | Status: MERGED | +2 | +1 |
| 105666,4 | Rename NetconfNotification to NotificationMessage | master | netconf | Status: MERGED | +2 | +1 |
| 105668,3 | Rename NetconfHelloMessage to HelloMessage | master | netconf | Status: MERGED | +2 | +1 |
| 105670,2 | sal-netconf-connector should not depend on notifications-api | master | netconf | Status: MERGED | +2 | +1 |
| 105682,7 | Clean up NotificationMessage | master | netconf | Status: MERGED | +2 | +1 |