Conversation
…n that can be used to skip converting values to primitive types.
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
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.
Given the xml request,
Our application needs to convert it into the following JSON format.
{ "sample": { "person": { "ID":"12999E105", "name":"Paul", "age":20 } } }Note the types of the values of "ID" (String) and "age" (int) fields.
With the configuration options available in JsonXMLConfigBuilder, we cannot disable the autoPrimitive feature selectively.
Therefore, currently we can only obtain one of the following results based on the setting of autoPrimitive configuration, but none of them are desirable.
autoPrimitive(true)
{"ID":1.2999E+109, "name":"Paul", "age":20 }autoPrimitive(false)
{ "ID":"12999E105", "name":"Paul", "age":"20" }To address this, we came up with a new configuration option for JsonXMLConfigBuilder; customRegex(String regex), which will make the above requirement possible.
ie, based on the value of customRegex, StAXON will skip the values of JSON fields that match the regex from being converted into a primitive type.