Description
(follow-up from #497)
Using Jackson-dataformat-ion 2.17
When constructing a new IonValueMapper
using constructor new IonValueMapper(onSystem)
modules are registered:
Constructor code:
public IonValueMapper(IonSystem ionSystem, PropertyNamingStrategy strategy) {
super(new IonFactory((ObjectCodec)null, ionSystem));
this.registerModule(new IonValueModule());
this.registerModule(new EnumAsIonSymbolModule());
this.setPropertyNamingStrategy(strategy);
}
However, when constructing using builder:
IonValueMapper.builder(ionSystem).build()
the modules are not registered, ultimately by chain of method calls, the following code is run in IonObjectMapper.class :
public static Builder builder(IonFactory streamFactory) {
return new Builder(new IonObjectMapper(streamFactory));
}
this creates an IonObjectMapper , without registering IonValueModule or EnumAsIonSymbolModule.
I think that the correct/expected behavior should be that using IonValueMapper.builder(...) should ultimately create a mapper which is the same as using constructor with the same parameters. Therefore it seems that there may need to be some changes or additional builder overrides added in IonValueMapper.
Workaround for this is just to not use builder to create IonValueMapper , or manually registering the modules.