[Fix #840] Allow overriding of default object mapper #845
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
By default, the internal object mapper will call findAndRegisterModules. If this is not the desired behaviour, implementors might replace it by a custom object mapper of their choice, either using ServiceLoader or explicit static call. Signed-off-by: fjtirado <ftirados@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
By default, the internal object mapper will call findAndRegisterModules. If this is not the desired behaviour, implementors might replace it by a custom object mapper of their choice
The ObjectMapperFactory can be set at any time, but it has to always return the same intance.
See #846 for alternative proposal that does the same but not force the factory to return always the same instance.