Prior to this commit, an error thrown by a `ExchangeFilterFunction` configured on a `WebClient` instance would be recorded as such by the client observation, but the response details would be missing from the observation. All filter functions and the exchange function (performing the HTTP call) would be merged into a single `ExchangeFunction`; this instance was instrumented and osberved. As a result, the instrumentation would only get the error signal returned by the filter function and would not see the HTTP response even if it was received. This means that the recorded observation would not have the relevant information for the HTTP status. This commit ensures that between the configured `ExchangeFilterFunction` and the `ExchangeFunction`, an instrumentation `ExchangeFilterFunction` is inserted. This allows to set the client response to the observation context, even if a later error signal is thrown by a filter function. Note that with this change, an error signal sent by a filter function will be still recorded in the observation. See gh-30059 |
||
---|---|---|
.github | ||
buildSrc | ||
ci | ||
framework-bom | ||
framework-docs | ||
framework-platform | ||
gradle | ||
integration-tests | ||
spring-aop | ||
spring-aspects | ||
spring-beans | ||
spring-context | ||
spring-context-indexer | ||
spring-context-support | ||
spring-core | ||
spring-core-test | ||
spring-expression | ||
spring-instrument | ||
spring-jcl | ||
spring-jdbc | ||
spring-jms | ||
spring-messaging | ||
spring-orm | ||
spring-oxm | ||
spring-r2dbc | ||
spring-test | ||
spring-tx | ||
spring-web | ||
spring-webflux | ||
spring-webmvc | ||
spring-websocket | ||
src | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.sdkmanrc | ||
CODE_OF_CONDUCT.adoc | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
README.md | ||
SECURITY.md | ||
build.gradle | ||
gradle.properties | ||
gradlew | ||
gradlew.bat | ||
import-into-eclipse.md | ||
import-into-idea.md | ||
settings.gradle | ||
update_copyright_headers.sh |
README.md
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 as reference 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@pivotal.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
Information regarding CI builds can be found in the Spring Framework Concourse pipeline documentation.
Stay in Touch
Follow @SpringCentral, @SpringFramework, and its team members on Twitter. In-depth articles can be found at The Spring Blog, and releases are announced via our news feed.
License
The Spring Framework is released under version 2.0 of the Apache License.