-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
UnrecognizedPropertyException when containing object is a Collection #76
Comments
Oh. I did indeed miss this one. Having 2.1 -> 2.2 regression is unusual. And I am guessing that 2.2.3 won't differ from 2.2.2? Or 2.3.0-rc1? |
Ah. The problem here is not so much XML, but the fact that a It is, however, possible to force Jackson to ignore the fact that it has a
and could help here. I'll see what else would be needed. |
FYI, I did some testing with 2.3.0. The following snippet
now throws the following exception:
Adding
|
Ok. Latter sounds like something to investigate. Without shape indication such usage can not be supported because although XML could actually represent such a use case (thanks to separation of attributes and elements!), JSON can not. So Jackson databinding can not support it across formats. But the failure to work with |
FYI, I have found a workaround with version 2.3.0:
|
Implement a workaround to Jackson errors with collections as described here: FasterXML/jackson-dataformat-xml#76 This closes #21 and should unblock us for #10. Signed-off-by: Pierre-Alexandre Meyer <pierre@mouraf.org>
Ok good to at least have a work-around! :) |
Works for 2.4.0 now. |
Consider the following test:
The test fails on 2.2.2 with the following exception:
The test passes though if I implement
Iterable<Value>
instead.Are Collections handled in a specific way? Is it possible to get the 2.1.2 behavior on 2.2.2?
The text was updated successfully, but these errors were encountered: