What would be the side effects from not using StdObjectMapperFactory?

13 views
Skip to first unread message

t.mcgee...@gmail.com

unread,
Jul 25, 2015, 2:39:51 AM7/25/15
to ektorp-discuss
If I where to use my own ObjectMapperFactory implementation rather than StdObjectMapperFactory, what would the side effects be?
It looks like the EktorpJacksonModule would not be registered to the ObjectMapper.
Since I'm not sure what the effects would be I plan to made an implementation that wraps StdObjectMapperFactory.
Like this:

public abstract class AbstractObjectMapperFactory implements ObjectMapperFactory{

private StdObjectMapperFactory mapperFactory = new StdObjectMapperFactory();


public ObjectMapper createObjectMapper() {

return decorate(mapperFactory.createObjectMapper());

}


public ObjectMapper createObjectMapper(CouchDbConnector connector) {

return decorate(mapperFactory.createObjectMapper(connector));

}

protected abstract ObjectMapper decorate(ObjectMapper mapper);

}


Henrik Lundgren

unread,
Aug 12, 2015, 4:36:34 AM8/12/15
to ektorp-discuss
The Ektorp module registers handlers the DocumentReferences annotation.
If you don't use them you will be fine.

//Henrik

--
You received this message because you are subscribed to the Google Groups "ektorp-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ektorp-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages