Sam Brannen
fd95ab16ba
ReflectivePropertyAccessor's canRead(), read(), and canWrite() methods previously constructed org.springframework.core.convert.Property instances without an explicit name, forcing Property#resolveName() to re-derive the property name from the accessor method via prefix matching. That heuristic incorrectly resolves record-style and other prefix-less accessor methods whose names embed or start with "get"/"is" (for example, budget(), issue(), or island()), and it also normalizes acronym-style JavaBean properties inconsistently (for example, getURL() resolves to "uRL" rather than "URL"). By the time these three methods construct a Property, they have already located the accessor method by searching for exactly the requested property name, so the resolved name is already known and verified. This commit passes that name through explicitly via the 4-arg Property constructor, bypassing Property#resolveName() entirely at these call sites. This commit also introduces tests in PropertyAccessTests to cover the following scenarios: - A genuine record accessor whose component name embeds or starts with a "get"/"is" prefix - The same scenario on a hand-written, non-record "data class" - The read() call site exercised directly, since it is otherwise unreachable once canRead() has warmed the cache - A boolean isXxx() getter, as a plain regression check - An acronym-style property with a decoy field to prove that the correct field (and its annotations) is now resolved for both reads and writes See gh-36911 Closes gh-37123
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.