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
we expect to end up with server state equivalent to:
Wrapper { base : Second { ignored : "ignoredValue", second : "secondValue" } }
most notably, the type of the inner object has changed from First to Second, the submitted state of the second property has been applied and the common value has been removed (PUT semantics) but the value of the unexposed ignored property has been properly transferred to the new instance.
This is currently broken as the object mapping tries to bind the values of the new object Second to the instance of the old one and ultimately doesn't apply the type change unless the class is annotated with Spring Data's @Immutable.
The text was updated successfully, but these errors were encountered:
We now replace the original value of polymorphic properties with the newly deserialized one if the type of the new one is different from the old one. We still copy all JSON ignored properties to the new instance to make sure that non-exposed, server-side state is retained. We apply the same handling for explicitly immutable source and/or target types.
Fixes#2130.
We now replace the original value of polymorphic properties with the newly deserialized one if the type of the new one is different from the old one. We still copy all JSON ignored properties to the new instance to make sure that non-exposed, server-side state is retained. We apply the same handling for explicitly immutable source and/or target types.
Fixes#2130.
We now replace the original value of polymorphic properties with the newly deserialized one if the type of the new one is different from the old one. We still copy all JSON ignored properties to the new instance to make sure that non-exposed, server-side state is retained. We apply the same handling for explicitly immutable source and/or target types.
Fixes#2130.
Given the following type arrangement:
, the original state of the resource being:
represented as
and a PUT request with this body
we expect to end up with server state equivalent to:
most notably, the type of the inner object has changed from
First
toSecond
, the submitted state of thesecond
property has been applied and thecommon
value has been removed (PUT
semantics) but the value of the unexposedignored
property has been properly transferred to the new instance.This is currently broken as the object mapping tries to bind the values of the new object
Second
to the instance of the old one and ultimately doesn't apply the type change unless the class is annotated with Spring Data's@Immutable
.The text was updated successfully, but these errors were encountered: