[MDSAL-113] Java Binding: groupings should not share classes with their instantiations Created: 11/Nov/15  Updated: 27/May/19  Resolved: 27/May/19

Status: Resolved
Project: mdsal
Component/s: Binding codegen
Affects Version/s: None
Fix Version/s: 4.0.0, Fluorine SR3, 3.0.7

Type: Bug
Reporter: Robert Varga Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
is blocked by MDSAL-237 Milestone: Implement Binding Specific... Resolved
Duplicate
duplicates MDSAL-182 Java binding v1: leafref up two conta... Resolved
External issue ID: 4625

 Description   

Sharing classes between things encapsulated in a grouping fails on perfectly valid models which define leafrefs to instances known only at instantiation.

A typical example is https://github.com/openconfig/public/blob/master/release/models/bgp/openconfig-bgp.yang#L588, which is valid, but since the resulting target is not known within the grouping itself, DTO generation fails.

Resolving this problem clearly requires two interfaces being generated 'list neighbor': one for the grouping version, which will be just a DataObject (as nothing else is known about it) and a second one for the final instantiation place, where the type is already known to be inet:address.


Generated at Wed Feb 07 20:08:40 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.