Hey,

I was wondering how do You normally deal with fields that contain
references that are not serializable. Say, we have a custom serialization
schema in Java that needs to serialize *LocalDateTime* field with
*ObjectMapper.*  This requires registering specific module for
*ObjectMapper* and this makes it not serializable (module contains some
references to classes that are not serializable).
Now, if You would initialize *ObjectMapper *directly in the field this will
cause an exception when deploying the job.

Normally I would do :

@Override
public byte[] serialize(Backup backupMessage) {
    if(objectMapper == null) {
        objectMapper = new ObjectMapper().registerModule(new JavaTimeModule());
    }
...
}

But I was wondering whether do You have any prettier option of doing this?

Thanks,
Dominik.

Reply via email to