Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XML containing xsi:nil is improperly parsed #366

Merged
merged 1 commit into from Oct 23, 2019

Conversation

lkorth
Copy link
Contributor

@lkorth lkorth commented Oct 23, 2019

XML containing a nested field with xsi:nil="true" causes following fields to be deserialized at the wrong hierarchy. I've added a unit test to demonstrate this incorrect behavior.

This appears to be a new bug in 2.10.0 as a result of 4938036

@cowtowncoder
Copy link
Member

Thank you for reporting this -- I'll merge the test, and refactor it to go under failing.
I don't know when I'll have time to look but it'd be good to straighten out aspects of xsi:nil (and related xsi attributes) for sure.

@cowtowncoder cowtowncoder merged commit 7f08139 into FasterXML:master Oct 23, 2019
cowtowncoder pushed a commit that referenced this pull request Oct 23, 2019
cowtowncoder added a commit that referenced this pull request Oct 23, 2019
cowtowncoder added a commit that referenced this pull request Oct 23, 2019
@lkorth lkorth deleted the xsi-nil-bug branch October 23, 2019 17:15
@lkorth
Copy link
Contributor Author

lkorth commented Oct 23, 2019

Thanks! Sorry, forgot to set the right base branch on the PR, it was supposed to be 2.11

@cowtowncoder
Copy link
Member

That's fine: I actually brought it back to 2.10 since it'd be good to fix there, not just 2.11 (although we'll see)

@cowtowncoder cowtowncoder added this to the 2.10.2 milestone Jan 5, 2020
cowtowncoder added a commit that referenced this pull request Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants