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
which may be relevant here. But other than that the new behavior is considered correct for String values: there really is no good way to indicate null in XML except by using xsi:nil="true" marker.
That marker is processed if FromXmlParser.PROCESS_XSI_NIL is true (which is the default setting).
Almost the same as #473 , apologies for not catching the changed behavior of strings at the same time as posting that issue.
Running version
2.11.4
using the following configuration:Parsing the following xml:
into the following bean:
usage:
The above JSON gets deserialized into the bean with the
name
property being set tonull
.With version
2.12.x
and newer thename
property becomes""
(empty string)Is this considered a bug? Or expected behavior for newer versions? Is there a way to revert to the previous behavior via config?
Thanks!
The text was updated successfully, but these errors were encountered: