Hi!
I’ve noticed that GraphhopperBundle.initialize(...)
does bootstrap.setObjectMapper(io.dropwizard.jackson.Jackson.newMinimalObjectMapper());
. This leads my Dropwizard application to fail during the config.yaml
parsing with error:
io.dropwizard.configuration.ConfigurationParsingException: config/config.yaml has an error:
* Unrecognized field at: server.applicationConnectors
Did you mean?:
- application_connectors
- application_context_path
- admin_connectors
- admin_min_threads
- allowed_methods
This is because my config.yaml follows camelCase naming strategy but minimalObjectMapper set up by GHBundle uses snake_case naming strategy.
If I store existing ObjectMapper before initializing GHBundle and set it back via bootstrap.setObjectMapper() then graphhopper fails during startup.
I’m wondering what would be the best solution for this problem. Is it a bug/limitation/requirements? Maybe Graphhoper bundle can use its own initialized ObjectMapper disregard of already registered one. I’m quite new to Dropwizard and this behaviour looks strange to me.