BindingCodecContext does not deal with unresolved leafrefs

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.

Environment

None

Activity

Show:

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Created June 16, 2021 at 8:36 AM
Updated March 10, 2025 at 9:21 AM