MongoJackModule can't be configured with a custom ObjectMapper in OSGi

[rakeshk15]

Since MongoJackModule is in internal package therefore it is not accessible to register the custom ObjectMapper.

Basically this doesn't work in OSGi

MongoJackModule.configure(myObjectMapper);

One option would be to expose the internal package as well without any code change and this will be fully backward compatible. However, it breaks strong encapsulation which OSGi provides.

Fix/workaround - We just need to add one more package in maven-bundle-plugin

org.mongojack,org.mongojack.internal

if it is ok then I could provide a PR.

Thanks,
Rakesh

[rakeshk15]

or probably some other programmatic way provided by the JacksonMongoCollectionBuilder class itself where we just configure the MongoJackModule once with the custom ObjectMapper as we don't need to configure it per collection.

[rlodge]

Would adding a static helper in org.mongojack that did the configuration work? I don't want to move the class and break backward compatibility.

e.g., something like:

org.mongojack.ObjectMapperConfigurer.configureObjectMapper(customObjectMapper)

[rakeshk15]

I completely agree on maintaining the backward compatibility.

Yes, a helper in exported package will work and org.mongojack is exported as per the manifest headers.