Support reversible JsonML mapping by avoiding implicit type conversion #70
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.
To introduce the opportunity to avoid implicit type conversion I have overloaded the parse method and added a new toJsonML(String) and a new toJsonML(XMLTokener) method using the overloaded parse method.
The changes have no impact on previously existing public methods - those should behave exactly as before.
One of the problems with the implicit type conversion is that xml data converted to json cannot be reverted to the original xml. Actually all non-string Json values are completely lost. This may be considered to be a separate problem of JSON.toString(JSONArray) which I did not try to solve directly, because for xml data converted using the new JsonML operations it is not relevant.
The following test case (groovy) illustrates the problems (testToJSONArray_*) and the solution (testToJsonML):