[Fix #840] Allow setting ObjectMapper before JsonUtils is initialized #846
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
fjtirado
force-pushed
the
Fix_#840a
branch
4 times, most recently
from
ab185c7 to
68636eb
Compare
fjtirado
changed the title
…onUtils is init Signed-off-by: fjtirado <ftirados@redhat.com>
ricardozanini
approved these changes
Oct 2, 2025
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.
Fix #840
Alternative implementation to #845
In this case the ObjectMapperFactory does not need to be singleton internally because it just invoked once, but it has to be set before JsonUtils is invoked, so it can only be initialized at application startup (which is probably desirable, but just in case)