Define a netconf-api capability model
(NETCONF-1015)
|
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0 |
| Type: | Sub-task | 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 |
|
The URNs used to identify NETCONF capabilities are used also as XML namespaces and we have the definitions of these strewn all across the codebase. While we are not yet ready to deal with the task of defining a complete object model of NETCONF capabilities, having a central place for their identifiers is helpful. Create CapabilityURN utility class, which will hold the Strings of the known capability URNs. Also eliminate duplicate definitions so that users rely exclusively on these constants. |
[NETCONF-1017]