Brian Clozel
cd110ad14e
Prior to this commit, `DataBinder` and the property accessor hierarchy relied on `PropertyAccessorUtils` and several independent scanners for property paths. This commit migrates all of them to `PropertyPath`, so there is exactly one parser deciding what a well-formed property path is, used identically for policy checks and for actual navigation. This removes long standing protected methods like A`getPropertyAccessorForPropertyPathi` and `getFinalPath` from `bstractNestablePropertyAccessor`. The path is now parsed exactly once per public entry point, via the new `resolvePropertyPath`, which returns a `ResolvedProperty`. Then, property navigation walks the parsed segment list rather than re-scanning partial strings. Any subclass overriding the removed method will need to adapt. This removal initially conflicted with gh-37252 (maxNestedPathDepth support). The public configuration remains but the actual behavior changed; it is replaced with `PropertyPath.Options` which enforces limit right after parsing, before property navigation begins. The exception thrown changes from `InvalidPropertyException` to `InvalidPropertyPathException`. This commmit also reverts the `map[']` / `map["]` quoting behavior from gh-36765 as it is incompatible with the new grammar. See gh-37275
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.