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
@JsonProperty's access mode should be inversed on server side and client side when both sides are sharing the same module class.
when using access = READ_ONLY with @JsonProperty, on the server side, that means property need to be serialized but can't be deserialized. but on the client side, the same property should be able to be deserialized but not to be serialized.
Is it good to have an out-of-box feature to do this inversion?
The text was updated successfully, but these errors were encountered:
Nothing to support it out-of-the-box, but you should be able to sub-class JacksonAnnotationIntrospector and override relevant methods to change the logic as necessary?
Or, alternatively, use mix-in annotations (but that may be more work for larger sets of types).
cowtowncoder
changed the title
inverse access of @JsonProperty so it can work differently on server side and client side
inverse access of @JsonProperty(access=) so it can work differently on server side and client side
Dec 2, 2020
cowtowncoder
changed the title
inverse access of @JsonProperty(access=) so it can work differently on server side and client side
Inverse access of @JsonProperty(access=) so it can work differently on server side and client side
Dec 2, 2020
@JsonProperty's access mode should be inversed on server side and client side when both sides are sharing the same module class.
when using access = READ_ONLY with @JsonProperty, on the server side, that means property need to be serialized but can't be deserialized. but on the client side, the same property should be able to be deserialized but not to be serialized.
Is it good to have an out-of-box feature to do this inversion?
The text was updated successfully, but these errors were encountered: