Jan 31st, 2011, 11:41 AM
Problem with MappingJacksonHttpMessageConverter.
I've just created the issue SPR-7924 but chances are that any of you may have an idea how to solve my problem in the meantime.
I'm unable to configure the ObjectMapper used by the MappingJacksonHttpMessageConverter created by <mvc:annotation-driven/>/AnnotationDrivenBeanDefinitionParser.
Do you have any idea how I can get my hands on the created instance of MappingJacksonHttpMessageConverter - even if it's involving something hacky like setAccessible+reflection?
Better yet, is there any "official" way to interfere with the automagically created message converters that I might have missed?
I searched and googled for two days but had no luck so far.
Tags for this Thread