Usage of ClassLoader.loadClass() in ConfigurationClassParser [SPR-17253]

[spring-projects-issues]

Dave Syer opened SPR-17253 and commented

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.

---

Affects: 5.0.8

Issue Links:

• Initial GraalVM native images (Substrate VM) support [SPR-16991] #21529 Initial GraalVM native images (Substrate VM) support ("is depended on by")

Referenced from: commits ad54472, c803ad7