[MDSAL-781] Eliminate BindingReflections Created: 01/Nov/22  Updated: 17/Jan/24

Status: Confirmed
Project: mdsal
Component/s: Binding runtime
Affects Version/s: None
Fix Version/s: 14.0.0

Type: Improvement Priority: Medium
Reporter: Robert Varga Assignee: Unassigned
Resolution: Unresolved 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

Issue Links:
Blocks
is blocked by BGPCEP-1016 Do not use BindingReflections.findQNa... Resolved
is blocked by MDSAL-783 Do not use BindingReflections.getQName Resolved
is blocked by CONTROLLER-2066 Do not use BindingReflections Confirmed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MDSAL-786 Remove BindingReflections.isAugmentat... Sub-task Resolved Robert Varga  
MDSAL-787 Remove BindingReflections.findHierarc... Sub-task Resolved Robert Varga  
MDSAL-788 Remove BindingReflections.resolveRpc{... Sub-task Resolved Robert Varga  
MDSAL-785 Replace and deprecate DataContainerCo... Sub-task In Review Samuel Schneider  
MDSAL-803 Rehost BindingReflections.getModuleIn... Sub-task Resolved Oleksandr Panasiuk  
Epic Link: AOT friendliness

 Description   

BindingReflections is a relict from the time when we did not have proper mdsal-binding-runtime support.
The functions of binding-runtime-spi, binding-dom-codec and binding-dom-adapter are making extensive use BindingReflections to match observed Binding classes to their DOM mapping.
This is counter-productive to AOT environments: mdsal-binding-runtime and its support classes should give us the information required to function in a manner which is completely independent of java.lang.reflect – rendering BindingReflections completely unncessary.



 Comments   
Comment by Robert Varga [ 26/Jun/23 ]

We have only a few methods remaining now:

  • findQname()
  • getQNameModule()
  • isBindingClass()

We should focus on eliminating individual callers as needed now.

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