Like Hantsy already said, accessing hardcoded mapper via `DatabindCodec.mapper()` is the only way I found it to be possible, too.
However, this is way too dirty and often results in code duplication. For example, it prevents you from having one, standardized ObjectMapper through whole project (except if you decide to use DatabindCodec.mapper() in whole project, but that would be super-dirty) and forces you tu configure separately one ObjectMapper for non-Vert.x-related components and Vert.x's own DatabindCodec.mapper(). More often then not, someone changes configuration in only one of those, causing hard-to-find bugs.
Allowing some form of setter/initializer for ObjectMapper that Vert.x uses would be much better.
> You received this message because you are subscribed to the Google Groups "vert.x" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com
> To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/54efac66-1770-4e47-9685-470410b8dc9bn%40googlegroups.com