Luca Burgazzoli created CAMEL-14101:
---------------------------------------
Summary: json-jackson dataformat: potential ObjectMapper
configuration clashes
Key: CAMEL-14101
URL: https://issues.apache.org/jira/browse/CAMEL-14101
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Luca Burgazzoli
Fix For: 3.x
The current default behaviour of the json-jackson data format is to try to
lookup an ObjectMapper instance to the registry and if not found to create a
new one.
In case one is found, the data format instance does customize it according to
its local properties but as the same ObjectMapper instance could be shared
among different json-jackson data formats, it may lead to inconsistencies or
unpredictable behaviors.
It would be nice to either:
- disable auto discovery by default so user can opt in
- if an ObjectMapper is given or found from the registry, discard local
customizations and log a warning/throw an error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
