[NETCONF-316] Netconf MD-SAL connector is treating prefixed XML as invalid Created: 14/Nov/16 Updated: 15/Mar/19 Resolved: 13/Oct/17 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Richard Kosegi | Assignee: | Alexis de Talhouët |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7176 |
| Description |
|
Logic in EditConfig is imposing requirements not defined by RFC (or at least I can't find such restriction). There are tools (eg. python ncclient) and devices (eg. https://www.juniper.net/documentation/en_US/junos15.1/topics/concept/netconf-session-rfc-compliant.html#jd0e89) which allows to use prefixed rpc elements and thus rendering connector-netconf-mdsal incompatible with them. This is message as received by ODL: Note "nc" prefix on root element. This is error : Error occurred while processing message I think problem is here: Element#getElementsByTagName() returns empty NodeList, because "target" element is in non-empty namespace. |
| Comments |
| Comment by Alexis de Talhouët [ 18/Nov/16 ] |
|
Proposed fix: https://git.opendaylight.org/gerrit/#/c/48483/ |