Closed coladict closed 7 years ago
Ok. It would be great to first submit a unit test to show a simple example, but a fix is of course very valuable too. Thank you for reporting this.
Still... I am not 100% sure I follow: given that back-reference is never written out, how could/should it matter? Or perhaps you meant @JsonManagedReference
which makes more sense?
Can not reproduce -- may be reopened with a reproducible test case (unit test).
When
@JsonSerialize
specifies a custom serializer in conjunction with@JsonBackReference
, it should not be ignored, as the reference is obviously meant for use during deserialization with such an explicit definition.This should apply when using
@JsonSerialize(as/converter/using)
and@JsonBackReference
on the same element, as well as when using@JsonSerialize(contentAs/contentConverter/contentUsing)
on the parent and@JsonBackReference
on the child.I have part of this working already in a patch, and it could be ready soon.