spring-framework

Spring Framework

Sam Brannen 18456dec52 Reintroduce FastClass in CGLIB class names for @⁠Configuration classes Given a @⁠Configuration class named org.example.AppConfig which contains @⁠Bean methods, in Spring Framework 5.3.x and previous versions, the following classes were created when generating the CGLIB proxy. org.example.AppConfig$$EnhancerBySpringCGLIB$$fd7e9baa org.example.AppConfig$$FastClassBySpringCGLIB$$3fec86e org.example.AppConfig$$EnhancerBySpringCGLIB$$fd7e9baa$$FastClassBySpringCGLIB$$82534900 Those class names indicate that 1 class was generated for the proxy for the @⁠Configuration class itself and that 2 additional FastClass classes were generated to support proxying of @⁠Bean methods in superclasses. However, since Spring Framework 6.0, the following classes are created when generating the CGLIB proxy. org.example.AppConfig$$SpringCGLIB$$0 org.example.AppConfig$$SpringCGLIB$$1 org.example.AppConfig$$SpringCGLIB$$2 The above class names make it appear that 3 proxy classes are generated for each @⁠Configuration class, which is misleading. To address that and to align more closely with how such generated classes were named in previous versions of the framework, this commit modifies SpringNamingPolicy so that generated class names once again include "FastClass" when the generated class is for a CGLIB FastClass as opposed to the actual proxy for the @⁠Configuration class. Consequently, with this commit the following classes are created when generating the CGLIB proxy. org.example.AppConfig$$SpringCGLIB$$0 org.example.AppConfig$$SpringCGLIB$$FastClass$$0 org.example.AppConfig$$SpringCGLIB$$FastClass$$1 Closes gh-31272		3 years ago
..
java	Reintroduce FastClass in CGLIB class names for @⁠Configuration classes	3 years ago
kotlin/org/springframework	Use consistently *KotlinTests naming for Kotlin tests	3 years ago
resources	Consolidate AspectJ test fixtures	3 years ago