[MDSAL-289] Binding v2 routedRPC to Action Created: 09/Aug/17 Updated: 16/Mar/19 Resolved: 16/Mar/19 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding V2 codegen |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Martin Ciglan | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8957 |
| Description |
|
this needs to be addressed for older models using routed RPC |
| Comments |
| Comment by Robert Varga [ 25/Jan/18 ] |
|
The idea here is that routed rpcs (i.e those which define a yang-ext rpc context reference) are semantically equivalent to YANG actions a should be treated the same way. This implies two things: Binding V2 should treat them as if they were actions defined in the specified context instance. Binding V1 should treat actions as routed rpcs and generate code as if a routed rpc were define with context instance at the place of action definition. |
| Comment by Robert Varga [ 25/Jan/18 ] |
|
This issue tracks the first part. A binding v1 tracker needs to be filed and linked here. |
| Comment by Robert Varga [ 16/Mar/19 ] |
|
Binding V2 is being removed in 4.0.0. |