AllEncompassingFormHttpMessageConverter does not prefer Jackson2 over JAXB for XML marshalling [SPR-13240]

[spring-projects-issues]

Bertrand Renuart opened SPR-13240 and commented

When configuring itself, AllEncompassingFormHttpMessageConverter doesn't prefer Jackson2 over JAXB for XML serialisation if Jackson2 is present on the classpath.

Because of this, it doesn't follow the behaviour of WebMvcConfigurationSupport or RestTemplate.

---

Affects: 4.2 RC3

Issue Links:

• Add Gson HttpMessageConverter [SPR-9488] #14123 Add Gson HttpMessageConverter
• Support Jackson2 based XML serialization/deserialization [SPR-11785] #16407 Support Jackson2 based XML serialization/deserialization
• Support Jackson based XML serialization in RestTemplate [SPR-12225] #16840 Support Jackson based XML serialization in RestTemplate
• AllEncompassingFormHttpMessageConverter prioritizes Jackson 2 XML over JSON [SPR-13309] #17894 AllEncompassingFormHttpMessageConverter prioritizes Jackson 2 XML over JSON

Referenced from: commits 9de824b

[spring-projects-issues]

Juergen Hoeller commented

As a further inconsistency, AllEncompassingFormHttpMessageConverter doesn't register GsonHttpMessageConverter either if GSON is present on the classpath (#14123).

I've closed both gaps for 4.2 GA now.

Juergen