ClassUtils could use long form of Class.forName [SPR-17333]

[spring-projects-issues]

Dave Syer opened SPR-17333 and commented

In ClassUtils.isPresent() we prefer ClassLoader.loadClass() to Class.forName(), even though there is a form of Class.forName() that includes the ClassLoader, and also provides the option to not initialize the class (which seems ideal for isPresent()).

(N.B. in Substrate VM Class.forName(className, false, currentLoader) works, for a class that is present, whereas classLoader.loadClass() fails.)

---

Affects: 5.1 GA

Issue Links:

• ClassUtils.forName fails to load class from ContextTypeMatchClassLoader [SPR-17452] #21984 ClassUtils.forName fails to load class from ContextTypeMatchClassLoader

Referenced from: commits spring-projects/spring-boot@b1d4cf4

[spring-projects-issues]

Dave Syer commented

Same thing applies to org.apache.commons.logging.LogAdapter in spring-jcl. It uses ClassLoader.loadClass() as a proxy for Class.forName().