OP-22069: Created a local HttpMethod ENUM as the one coming from spring is not serialisable trough ObjectMapper #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rahul-chekuri
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://devopsmx.atlassian.net/browse/OP-22069
As part of CVE fixes, spring-web has been upgraded. In the new package, HttpMethod is converted to a class from Enum. Due to this change, ObjectMapper cannot serialize @org.springframework.http.HttpMethod, so we created this Enum to support serialization.
Root Cause: As part of CVE fixes we have upgraded the spring version. The newer version has HttpMethod as a Class instead of an Enum. This leads to serialisation issues.
Solution: Create a local copy of the old Enum HttpMethod and use it wherever required.