[MDSAL-10] Support anydata and anyxml statements in Binding V1 Created: 09/Apr/14 Updated: 06/Aug/19 Resolved: 06/Aug/19 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | Binding codegen, Binding runtime |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.2 |
| Type: | Epic | Priority: | Highest |
| Reporter: | Milos Fabian | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Environment: |
Operating System: Windows |
||
| Issue Links: |
|
||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||
| Description |
|
-anyxml statement is not generated into Java APIs, mapping service is not provided |
| Comments |
| Comment by Mayank Agarwal [ 17/Apr/14 ] |
|
More details from Milos: The first problem is if yang model contains anyxml node - it is skipped during yang-to-java mapping (code generating). For example, you can look at the yang model in controller/opendaylight/md-sal/sal-remote and there is „notification data-changed-notification“ having „anyxml data“ node, so if you look at DataChangeEvent.java interface (generated from the yang model), there no such field representing anyxml data node. |
| Comment by Mayank Agarwal [ 18/Apr/14 ] |
|
Gerrit Patch: |
| Comment by Tony Tkacik [ 24/Jul/14 ] |
|
Moved to post-helium since this is change of Binding Specification. |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
Move to MDSAL |
| Comment by Martin Ciglan [ 07/Jun/17 ] |