This repository was archived by the owner on May 12, 2021. It is now read-only.
less memory consumption in json deserializer #9
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is attempt to avoid reading the json into memory.
See comment in JavaxJsonDeserializer .
// JSR-353 Does not allow reading "out of structure" values
...
// In the meantime, a poor man's implementation reading the json into memory will do.
There is no way how via javax.json api read 'out of structure' data for all needed cases.
Ie. parsing only Instant value.
( or at least I haven't found how to do it with latest Johnzon and glassfish impl. )
This solution doesn't handle adapters properly I assume.