[MDSAL-147] Binding codegen: RFC6020 defines the order of evaluation for union members (binding spec v2) Created: 05/Apr/16  Updated: 09/Mar/18  Resolved: 03/Apr/17

Status: Resolved
Project: mdsal
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Martin Ciglan 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-49 Do not generate Builders for Union types Resolved

 Description   

+++ This bug was initially created as a clone of MDSAL-49 +++

Our codegen requires users to manually instantiate the builder for union types, which parses a string. RFC6020 (http://tools.ietf.org/html/rfc6020#section-9.12), specifies the following:

When a string representing a union data type is validated, the string
is validated against each member type, in the order they are
specified in the "type" statement, until a match is found.

This removes enough ambiguity, such that we can auto-generate a proper builder. Generate the builder (still in src/main, as we need to maintain compatibility).

 Comments   
Comment by Martin Ciglan [ 03/Apr/17 ]

this looks like an unnecessary duplicate of initial bug
https://bugs.opendaylight.org/show_bug.cgi?id=2289
which is already set for Binding spec v2 and valid,
so I am closing this one.

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