Reduce use of deprecated APIs#4334
Merged
fmbenhassine merged 1 commit intospring-projects:mainfrom Mar 29, 2023
hpoettker:use-less-deprecated-apis
Merged
Reduce use of deprecated APIs#4334fmbenhassine merged 1 commit intospring-projects:mainfrom hpoettker:use-less-deprecated-apis
fmbenhassine merged 1 commit intospring-projects:mainfrom
hpoettker:use-less-deprecated-apis
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The following APIs are currently deprecated:
org.springframework.util.Base64Utilsorg.springframework.util.SerializationUtils#deserializejava.lang.reflect.AccessibleObject#isAccessibleThis PR replaces their use in the code base:
Base64Utilsis replaced by usingjava.util.Base64directly.SerializationUtils#deserializeis replaced by usingObjectInputStreamdirectly.isAccessibleare removed as they are not necessary when the respective objects are not cached.I've also replaced
SerializationUtils#serializeinDefaultExecutionContextSerializerby usingObjectOutputStreamdirectly. This way, less objects are created during execution and the code for serialization and deserialization matches more closely.There are also some straight-forward deprecations within the code base that have been addressed.