Sam Brannen
b96592e4af
Prior to this commit, LogAccessor's CharSequence-based logging methods delegated directly to the corresponding method on the underlying commons-logging Log instance without first checking whether the target level was enabled. This differed from the Supplier-based overloads, which have checked isXxxEnabled() before delegating since Spring Framework 5.2.9. That asymmetry was harmless as long as spring-jcl supplied the underlying Log implementation, since its SLF4J adapter itself checked the level before rendering the message. However, since Spring Framework 7 replaced spring-jcl with Apache commons-logging, whose SLF4J adapters call String.valueOf(message) unconditionally, any CharSequence argument -- most notably a LogMessage supplied via LogMessage.format(...) or LogMessage.of(...) -- is now rendered eagerly, even when the corresponding level is disabled. Since LogMessage exists specifically to defer that work, and the idiom is used extensively throughout the framework and its portfolio projects, this leads to unnecessary computation and allocation whenever logging is disabled. To address this, this commit adds the same isXxxEnabled() guard to all twelve CharSequence-based methods in LogAccessor, matching the existing Supplier-based overloads and making LogAccessor's laziness guarantee independent of the underlying Log implementation. This commit also introduces LogAccessorTests, which verifies that a lazily rendering LogMessage passed to one of the CharSequence-based methods is only rendered when the corresponding level is enabled. See gh-25741 Closes gh-37266
Spring Framework 
This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects are often referred to simply as "Spring".
Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section of the reference documentation for a more complete introduction.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@spring.io.
Access to Binaries
For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.
Documentation
The Spring Framework maintains reference documentation (published and source), GitHub wiki pages, and an API reference. There are also guides and tutorials across Spring projects.
Micro-Benchmarks
See the Micro-Benchmarks wiki page.
Build from Source
See the Build from Source wiki page and the CONTRIBUTING.md file.
Continuous Integration Builds
CI builds are defined with GitHub Actions workflows.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on 𝕏. In-depth articles can be found at The Spring Blog, and releases are announced via our releases feed.
License
The Spring Framework is released under version 2.0 of the Apache License.