[NETCONF-356] Provide an optional mode to parse NETCONF messages ignoring namespaces Created: 28/Feb/17 Updated: 04/May/20 |
|
| Status: | Confirmed |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Ryan Goulding | Assignee: | David Goldberg |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
This enhancement has been asked for several times. One such example is in this email thread [0]. [0] https://lists.opendaylight.org/pipermail/netconf-dev/2017-February/000934.html |
| Comments |
| Comment by David Goldberg [ 07/Mar/17 ] |
|
I created a fix for this here: |
| Comment by Tomas Cere [ 29/Jun/17 ] |
|
That patch only ignores schemas with empty namespace from netconf-state, this bug is about parsing messages with empty namespace |
| Comment by Robert Varga [ 27/Aug/18 ] |
|
gdavid@hpe.com any update to your patch? Are you still working on this? |
| Comment by Jamo Luhrsen [ 04/May/20 ] |
|
The original patch is merged, but to tcere's point, I don't know if it fully addresses parsing messages with |