Adding a more direct way to add (de)serializers when building an ObjectMapper?

[soc]

Currently it is done like this:

  private final JsonMapper jsonMapper = JsonMapper.builder()
      .addModule(new SimpleModule()
          .addSerializer(Grid.class, new GridSerializer())
          .addDeserializer(Grid.class, new GridDeserializer()))
      .build();

I believe this pattern of "call addModule, then create a SimpleModule, then add (de)serializers on that" is not very intuitive or discoverable, especially for beginners.

Would it be possible to provide a more "direct" way of doing this, perhaps either by

• explicit addSerializer/addDeserializer/... methods on JsonMapper, or by
• exposing a context (similar to how it is done with SetupContext for JacksonModule sub-classes) that provides such an API?

What do you think?

Thanks,

Simon

[cowtowncoder]

-1 from me. In general having to add (de)serializers manually should not be common thing to do (over using shared modules). So I don't necessarily even want beginners to use that path unless other mechanisms fail.

[soc]

Interesting, I was not aware of that usage pattern.

The only place where modules are created in the code-base I'm working on is inline in that addModule call.

Instead what's shared are the JsonMappers. Is there anything I'm missing when doing that?

[cowtowncoder]

You can use JsonMapper.rebuild() to get a builder for creating differently configured mappers: this creates new mapper instance.
You just cannot add modules directly on mappers as they are truly immutable in 3.x.

[soc]

No, I'm asking what's the benefit of sharing modules instead of sharing the mappers.

[cowtowncoder]

@soc just if you have multiple commonly used (de)serializers, packaging things together.
But sharing mappers works too and if that works nicely yeah no real benefits -- no need to create shared modules if you share mappers anyway.

[soc]

Ok, thanks!