[MDSAL-398] Optimize LazyDataObject method dispatch Created: 16/Nov/18  Updated: 22/Nov/18  Resolved: 22/Nov/18

Status: Resolved
Project: mdsal
Component/s: Binding runtime
Affects Version/s: None
Fix Version/s: Fluorine SR2, Oxygen SR4, 3.0.2

Type: Improvement Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MDSAL-399 Use MethodHandles in LazyDataObject t... Resolved

 Description   

LazyDataObject method dispatch is a bit sub-optimal, as it does not take advantage:

  1. Java 8's Method.getArgumentCount()
  2. Ability to switch on strings coupled with method names being interned
  3. The fact that getters have zero arguments and hence are uniquely identified by their name

Address these issues, hence further improving LazyDataObject hot path.
Generated at Wed Feb 07 20:09:42 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.