IncompatibleClassChangeError after upgrading to Spring Framework 7.0.3 (HttpHeaders & MultiValueMap) java 25

[rani111agrawal]

We are facing an issue after upgrading our application from Spring Framework 6.x to 7.0.3.
This issue occurs while calling an API that is used behind AWS CloudFront.

After the upgrade, we get the following runtime error:

java.lang.IncompatibleClassChangeError:
Class org.springframework.http.HttpHeaders does not implement
the requested interface org.springframework.util.MultiValueMap
at org.springframework.http.HttpHeaders.isEmpty(HttpHeaders.java:1897)
at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:227)
The error happens when returning a ResponseEntity from a controller method.
public ResponseEntity postDynamicField(@RequestBody CloudFront cloudFront) {
CloudFront fetchedCloudFront = awsCFService.getSignedURL(cloudFront);
return ResponseEntity.status(HttpStatus.CREATED).body(fetchedCloudFront);
}

Could you help in resolution.

Technical Stack
Spring 7.0.3
Java 25
aws-java-sdk-cloudfront 1.12.797

[bclozel]

Your application is mixing spring versions. You probably have a spring-webmvc artifact which is not aligned on 7.0.x.

Please check your spring framework dependency versions and report back.

You can try and apply the spring framework BOM to consistently get a good set of dependencies.

<dependencyManagement>
	<dependencies>
		<dependency>
			<groupId>org.springframework</groupId>
			<artifactId>spring-framework-bom</artifactId>
			<version>7.0.3</version>
			<type>pom</type>
			<scope>import</scope>
		</dependency>
	</dependencies>
</dependencyManagement>

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.