clear forced xsi:type attribute state in ToXmlGenerator.writeName - #909
Open
Sahana2524 wants to merge 1 commit into
Open
clear forced xsi:type attribute state in ToXmlGenerator.writeName#909Sahana2524 wants to merge 1 commit into
Sahana2524 wants to merge 1 commit into
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 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.
writeName's syntheticxsi:typehandling forces attribute mode and the XSI namespace onto the next value, and only the bean-serializer path clears it (by assigning the next name throughsetNextName):Map/JsonNode/@JsonAnyGetterkey ofxsi:typeleaves every following sibling as anxsi:-prefixed attribute instead of an element{"xsi:type":"A","type":"B"}emits a duplicatexsi:typeattribute, so the module produces XML it can no longer read back{"xsi:type":"T","nil":"true"}emitsxsi:nil="true", so the whole document reads back asnullClears the forced state on the next
writeNamefor the content-driven case; the bean path already reset it viasetNextName, so legitimate polymorphic output is unchanged.