You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue only appears to happen when the field name and annotation names match AND there is a setter. From version 2.8.8+ this throws an exception. I can fix this on our end with any of the mentioned fixes just thought I would mention it.
The text was updated successfully, but these errors were encountered:
I can not reproduce this with 2.9 (pre-2.9.6). May be reopened with failing test case.
(test class Issue274PropertyNameTest slightly simplified -- could be something I did, but I can't see any reason).
I'm not sure exactly how this was tracked down but our XML serializer started breaking between version
2.8.7
and2.8.8
with aIt appears the actual change was in jackson-databind-2.8.7-2.8.8 since there are no notable changes in jackson-dataformat-xml-2.8.7-2.8.8 but seems related to the XML annotations. Here is the best example I could come up with to reproduce.
However, commenting out the XML annotation will work.
Removing the setter and keeping the annotation will also work.
Fixing the case of the field will also work.
And finally commenting out MapperFeature.ACCEPT_CASE_INSENSITIVE_PROPERTIES seems to work.
//xm.enable(MapperFeature.ACCEPT_CASE_INSENSITIVE_PROPERTIES);
This issue only appears to happen when the field name and annotation names match AND there is a setter. From version 2.8.8+ this throws an exception. I can fix this on our end with any of the mentioned fixes just thought I would mention it.
The text was updated successfully, but these errors were encountered: