Closes GH-32087

Comment From: jhoeller

@quaff thanks for the PR which I'm mostly using for my fix for #32087. However, I'm avoiding the extra constraints (and extra overhead) in ClassUtils.getMostSpecificMethod since that is being called in rather expensive code paths. The check in BridgeMethodResolver should be sufficient for our purposes here.

Comment From: quaff

@quaff thanks for the PR which I'm mostly using for my fix for #32087. However, I'm avoiding the extra constraints (and extra overhead) in ClassUtils.getMostSpecificMethod since that is being called in rather expensive code paths. The check in BridgeMethodResolver should be sufficient for our purposes here.

It's better to amend the commit to revert ClassUtils.getMostSpecificMethod part, contributors like be the author.