[
https://issues.apache.org/jira/browse/CAMEL-25338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123334#comment-18123334
]
Federico Mariani commented on CAMEL-25338:
------------------------------------------
Draft PR: https://github.com/apache/camel-spring-boot/pull/2018
_Claude Code on behalf of Croway_
> camel-spring-boot - document Jackson 2 / Jackson 3 usage and migration
> ----------------------------------------------------------------------
>
> Key: CAMEL-25338
> URL: https://issues.apache.org/jira/browse/CAMEL-25338
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot, documentation
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
>
> Since 4.19 Camel Spring Boot runs on Spring Boot 4 (Jackson 3 by default),
> and Camel ships two parallel Jackson module families (camel-jackson* /
> camel-jackson3*) that register the same data format names, transformers,
> configurer and starter beans. There is no Jackson guidance in
> docs/spring-boot today.
> Add a page covering:
> * only one Camel Jackson line per application (both starters ->
> BeanDefinitionOverrideException; starters bringing camel-jackson transitively
> -> classpath order silently decides the data format, and
> camel.dataformat.jackson.* is dropped when Jackson 2 wins)
> * Kamelet schema resolution only works with the Jackson 2 modules
> * upgrading from 4.18 while staying on Jackson 2 (auto-discover-object-mapper
> no longer finds a Spring mapper; spring.jackson2.* prefix)
> * moving to Jackson 3: Camel-specific configuration changes (feature
> prefixes, modules, auto-discovery caveats, onException), payload changes,
> keeping the Jackson 2 format for Camel only
> * Jackson versions come from the Spring Boot BOM
> All statements were reproduced against Camel Spring Boot 4.22.1 / Spring Boot
> 4.1.1. Related to CAMEL-22857.
> _Claude Code on behalf of Croway_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
