[NETCONF-361] Document expected behavior with respect to RPC implicit input and output Created: 07/Mar/17 Updated: 15/Mar/19 Resolved: 07/Mar/17 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| 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: | 7914 |
| Description |
|
In Carbon, Previously, Restconf RPC behavior was different between missing and empty elements. Namely, missing input statement required no data, empty input required '{"input":{}}' as data. Also, missing output resulted in no response text, empty output resulted in '{"output":{}}'. The output difference is not relevant to CSIT tests (the text was not checked). But the input difference is relevant, as empty data now fails [0]. This Bug is for Restconf to decide whether empty data is to be accepted, to make calls backward compatible with Boron-SR2. If it is decided that Carbon will keep current backward incompatibility, the error message should be fixed anyway (from 500 to 400 with relevant message). |
| Comments |
| Comment by Vratko Polak [ 07/Mar/17 ] |
|
If the current |
| Comment by Vratko Polak [ 07/Mar/17 ] |
|
Turns out the compatibility patches were already prepared, just not merged right away. Currently Carbon should be fixed (not verified): https://git.opendaylight.org/gerrit/52882 |