Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-16757

AopUtils.getMostSpecificMethod should expose dynamic proxy class methods

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.6, 5.1 RC1
    • Component/s: None
    • Labels:
    • Last commented by a User:
      true

      Description

      After the changes for SPR-16677AopUtils.getMostSpecificMethod does not resolve proxy class methods anymore. It turns out that this is a regression for some scenarios, in particular for dynamic proxies as targets with their redeclaration of all interface methods at the most specific level. In order for Method.getDeclaringClass() to expose the concrete type again in such scenarios, we should rather revisit that algorithm to not specifically handle proxy class methods, just consistently skipping resolution for CGLIB cases (in particular configuration classes and lookup-method classes) as we did in a few places before already.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              juergen.hoeller Juergen Hoeller
              Reporter:
              juergen.hoeller Juergen Hoeller
              Last updater:
              Spring Issues Spring Issues
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 23 weeks, 4 days ago