Domain types serialization without depending on annotations from Jackson library.

[gusega]

Hi all,

I have my domain model and I don't want to make it depend on jackson annotations.

How do I enable json serialization for my model classes? Do I have to create POJOs for my domain types in the contexts where I want to serialize them or does jackson databind has some facilities to use instead? That is, to enable serialization at the call site.

Thanks.

[JooHyukKim]

@gusega More concrete explanation, preferrably with example would be helpful!

[gusega]

@JooHyukKim I have a module where I have my domain model, which does not know about serialization. There I have classes such as, for simplicity,

record Person(String name, int age) {}

In some other module of my applicaition, I want to serialize my domain module. To do that I need certain annotations, maybe a couple of constructors etc, which I only need for serialization. Normally I would create a copy of my Person class just for serialization purposes and put all those annotations on it. And then covert from Person to SerializedPerson every time I want to serialize it.

I wonder if jackson has something that simplifies this, provided that I already have almost exactly what I need in my domain model, but just need to adjust it slightly.

Alternative would be to include necessary serialization adaptations in the domain model.

[cowtowncoder]

Jackson has concept of "mix-in annotations" that may be helpful in associating annotations to use for a domain class, without actually adding annotations (but working like they were added).

Other than that, I am not sure there is anything. But it would also be good to show hypothetical usage like you envision it -- I am not quite sure I understand intended usage; what problems domain classes have that prevent serialization without use of annotations, for example.

[gusega]

@cowtowncoder thanks a lot. For now the only thing that comes to mind that my domain classes otherwise dont need is factory methods and IgnoreUnknownProperties(true) annotations.

[cowtowncoder]

Ok that makes sense. Factory methods would probably need mix-in annotations; for IgnoreUnknownProperties there is the Global DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES if global defaulting works (not if only some types are to have lenient handling).