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.

Sign up for GitHub

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

Jump to bottom

Conflict between @JsonIdentityInfo and Unwrapped Lists #286

Open
rupert-madden-abbott opened this issue May 5, 2018 · 2 comments
Open

Conflict between @JsonIdentityInfo and Unwrapped Lists #286

rupert-madden-abbott opened this issue May 5, 2018 · 2 comments
Milestone
2.15.0

Comments

@rupert-madden-abbott
Copy link

rupert-madden-abbott commented May 5, 2018 •
edited

Jackson version: latest (I will submit a failing test).

When using JsonIdentityInfo, if both sides of the reference contain an unwrapped list, then various exceptions are thrown depending on the exact structure of the rest of the XML. It looks like the parser has stumbled off course somehow and swallows up subsequent elements, getting itself into a bit of a mess.

For the moment, the workaround is to not use unwrapped lists on both sides of the relationship when using JsonIdentityInfo
@cowtowncoder
Copy link
Member

Sounds entirely plausible. Handling of unwrapped case is complicated thing and barely working even without type and/or object ids.

cowtowncoder added a commit that referenced this issue May 7, 2018
@cowtowncoder
Merge pull request #287 from rupert654/master
052675f 
Add failing test for #286
cowtowncoder added a commit that referenced this issue Mar 21, 2023
@cowtowncoder
Test refactoring (test for #286 now passes)
9427352
@cowtowncoder cowtowncoder added this to the 2.15.0 milestone Mar 21, 2023
@cowtowncoder
Copy link
Member

This has been fixed at some point it seems; marking as fixed for 2.15.

@cowtowncoder cowtowncoder changed the title Conflict between JsonIdentityInfo and Unwrapped Lists Conflict between @JsonIdentityInfo and Unwrapped Lists Mar 21, 2023
cowtowncoder added a commit that referenced this issue Mar 21, 2023
@cowtowncoder
Marked #286 as fixed
9f2c351
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.15.0
Development

No branches or pull requests
2 participants
@cowtowncoder @rupert-madden-abbott