Set managed Jsonb provider - #18
Draft
lampajr wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Andrea Lamparelli <a.lamparelli95@gmail.com>
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
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.
This seems to be a workaround to the problem raised #17, in particular #17 (comment).
With this fix we are injecting a default/managed
Jsonbinstance avoiding Resteasy to keep callinggetDelegateeverytime a new response needs to be serialized causing quite evident degradation in the performance of this very simple application.As mentioned I think this is just a workaround as I was expecting Resteasy to cache the Jsonb even when not explicitly provided but since I am not that familiar on this part I'd like to get some other feedback on the best approach here.
Before
After
