Describe the Problem
After upgrading our application to use spring boot 4 (uses spring 7), we are not able to run the application because of the error:
An attempt was made to call a method that does not exist. The attempt was made from the following location:
com.sap.cloud.sdk.services.openapi.apiclient.ApiClient.addDefaultHeader(ApiClient.java:341)
The following method did not exist:
'java.util.List org.springframework.http.HttpHeaders.remove(java.lang.Object)'
The calling method's class, com.sap.cloud.sdk.services.openapi.apiclient.ApiClient jar:file:.../.m2/repository/com/sap/cloud/sdk/datamodel/openapi-core/5.32.0/openapi-core-5.32.0.jar!/com/sap/cloud/sdk/services/openapi/apiclient/ApiClient.class
The called method's class, org.springframework.http.HttpHeaders, is available from the following locations:
jar:file:.../.m2/repository/org/springframework/spring-web/7.0.8/spring-web-7.0.8.jar!/org/springframework/http/HttpHeaders.class
The called method's class hierarchy was loaded from the following locations:
org.springframework.http.HttpHeaders: file:.../.m2/repository/org/springframework/spring-web/7.0.8/spring-web-7.0.8.jar
Action:
Correct the classpath of your application so that it contains compatible versions of the classes com.sap.cloud.sdk.services.openapi.apiclient.ApiClient and org.springframework.http.HttpHeaders
Propose a Solution
Support Spring 7
Describe Alternatives
No response
Affected Development Phase
Development
Impact
Blocked
Timeline
Considering that Spring 6.2 is end of life already, as soon as possible.
Describe the Problem
After upgrading our application to use spring boot 4 (uses spring 7), we are not able to run the application because of the error:
Propose a Solution
Support Spring 7
Describe Alternatives
No response
Affected Development Phase
Development
Impact
Blocked
Timeline
Considering that Spring 6.2 is end of life already, as soon as possible.