[MDSAL-670] BindingCodecContext does not deal with unresolved leafrefs Created: 16/Jun/21  Updated: 22/Jan/24

Status: In Progress
Project: mdsal
Component/s: Binding runtime
Affects Version/s: 7.0.7, 6.0.10
Fix Version/s: 14.0.0, 13.0.1

Type: Bug Priority: Medium
Reporter: Robert Varga Assignee: Ivan Hrasko
Resolution: Unresolved Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by MDSAL-669 Retain grouping/uses instantiation ve... Resolved
Issue split
split from MDSAL-668 Issue serializing object type define... Resolved

 Description   

As noted in analysis of MDSAL-668, we have an edge case where BindingCodecContext assumes no-op translation when it sees a wildcard or Object return. This typically comes from leafref type that cannot be resolved at its definition.

These leafrefs are eventually resolved somewhere along the instantiation chain, so that the appropriate codec can be located. Rework type lookup to work with instantiation information exposed via MDSAL-669 and pass it around streaming pipeline as needed.


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