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

Usage of ClassLoader.loadClass() in ConfigurationClassParser

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Complete
    • Affects Version/s: 5.0.8
    • Fix Version/s: 5.0.9, 5.1 RC3
    • Component/s: Core, Core:DI
    • Labels:
      None
    • Last commented by a User:
      true

      Description

      In ConfigurationClassParser we explicitly call ClassLoader.loadClass() which is a bit odd, given that we have ClassUtils to do that work for us, and that is the "normal" pattern in Spring internally. It wouldn't affect any regular apps if we refactored to use ClassUtils (I tried it and the tests all pass). It would affect AOT native images in a positive way: the ClassLoader is null in that case, but Class.forName() actually works.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              juergen.hoeller Juergen Hoeller
              Reporter:
              david_syer Dave Syer
              Last updater:
              Spring Issuemaster
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                1 year, 40 weeks, 6 days ago