[CAMEL-17956] JSONPath option to use global registered ObjectMapper

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.14.2, 3.16.0
• Fix Version/s: 3.17.0
• Component/s: camel-jsonpath
• Estimated Complexity: Advanced
• Assignee: Karen Lease
• Reporter: Mikael Andersson Wigander
• Created: 13/Apr/22 04:58
• Updated: 13/Feb/23 14:58
• Resolved: 05/May/22 15:19

Description

I have discovered that when using JSONPath in a route, the implementation does not use any ObjectMapper registered, it uses it's own.

JacksonMappingProvider.class

public class JacksonMappingProvider implements MappingProvider {

private final ObjectMapper objectMapper;

public JacksonMappingProvider() {
this(new ObjectMapper());
}

public JacksonMappingProvider(ObjectMapper objectMapper) {
this.objectMapper = objectMapper;
}

However, when using .jsonpathWriteAsString(), this uses global registered ObjectMapper.

JacksonJsonAdapter.class

@Override
    public String writeAsString(Object value, Exchange exchange) {
        ObjectMapper mapper = resolveObjectMapper(exchange.getContext().getRegistry());
        try {
            return mapper.writeValueAsString(value);
        } catch (Throwable e) {
            // ignore because we are attempting to convert
        }

        return null;
    }

It does not go through the JsonPathEngine so it seems it's a completly differrent implementation however still defined within JSONPath language as in this documentation:

https://camel.apache.org/components/3.14.x/languages/jsonpath-language.html#_split_json_data_into_sub_rows_as_json

Issue Links

• relates to: CAMEL-19035 Camel-jsonpath is parsing whole json payload from 3.10.0
• links to: GitHub Pull Request #7544