[YANGTOOLS-663] RPC definition should implicitly define input/output Created: 04/Oct/16 Updated: 10/Apr/22 Resolved: 13/Mar/17 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Igor Foltin |
| 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: | 6856 |
| Description |
|
Based on the discussion at https://mailarchive.ietf.org/arch/msg/netmod/tjxTtCehVLeSScoV84ggmvpNWb0, an RPC declaration should result in input and output statement being implicitly present even if they are not declared. Hence the augmentation in the thread should succeed, just as if the rpc was defined with an empty input statement. |
| Comments |
| Comment by Igor Foltin [ 25/Nov/16 ] |
| Comment by Martin Ciglan [ 28/Feb/17 ] |
|
corresponding patch for MD-SAL: |
| Comment by Igor Foltin [ 03/Mar/17 ] |
|
corresponding patch for controller: |
| Comment by Robert Varga [ 05/Mar/17 ] |
|
fixed on master, boron needs a manual cherry pick. |
| Comment by Igor Foltin [ 07/Mar/17 ] |
|
fix on boron: https://git.opendaylight.org/gerrit/#/c/52926/ |