I\'m having a bidirectional many to many relationship in my entities. See the example below:
public class Collaboration {
@JsonManagedReference(\"COLLAB
I ended up implementing the following solution.
One end of the relationship is considered to be the parent. It does not need any Jackson related annotation.
public class Collaboration {
private Set tags;
}
The other side of the relationship is implemented as follows.
public class Tag {
@JsonSerialize(using = SimpleCollaborationSerializer.class)
private Set collaborations;
}
I'm using a custom serializer to will make sure that no cyclic references will occur. The serializer could be implemented like this:
public class SimpleCollaborationSerializer extends JsonSerializer> {
@Override
public void serialize(final Set collaborations, final JsonGenerator generator,
final SerializerProvider provider) throws IOException, JsonProcessingException {
final Set simpleCollaborations = Sets.newHashSet();
for (final Collaboration collaboration : collaborations) {
simpleCollaborations.add(new SimpleCollaboration(collaboration.getId(), collaboration.getName()));
}
generator.writeObject(simpleCollaborations);
}
static class SimpleCollaboration {
private Long id;
private String name;
// constructors, getters/setters
}
}
This serializer will only show a limited set of the properties of the Collaboration entity. Because the "tags" property is omited, no cyclic references will occur.
A good read about this topic can be found here. It explains all possibilities when you're having a similar scenario.