[CAMEL-14101] json-jackson dataformat: potential ObjectMapper configuration clashes

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: camel-jackson
• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: Luca Burgazzoli
• Created: 23/Oct/19 09:26
• Updated: 30/Oct/19 09:09
• Resolved: 30/Oct/19 09:09

Description

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