Hello, I've updated the camel-spring-boot-examples <https://github.com/apache/camel-spring-boot-examples/> repository to use Camel 4.19.0-SNAPSHOT and Spring Boot 4 and the experience was not bad, this is the commit <https://github.com/apache/camel-spring-boot-examples/commit/102730d75f53dd61606ef8e5812e0722eeec79ba> and as you can see all the examples are still supported and working fine. The actual work will be on Spring Boot 4 upgrade:
- junit5 -> 6 - *camel-test-spring-junit5* -> *camel-test-spring-junit6 *with some package updates - some dependencies need to be updated like *spring-boot-starter-web* -> *spring-boot-starter-webmvc* - jackson3 (packages updates mostly). I've used the Spring Boot 4 OpenRewrite recipe to update the examples, and it did most of the work automatically. I thought it was harder than expected. You can monitor the Camel 4.19 upgrade guide <https://github.com/apache/camel/blob/4ca46d5ceae626df0f3e4c908faebd4b80f8dc23/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_19.adoc> we'll include components removal and potential issues as we find them. Right now you can already generate a new Camel Spring Boot application using the archetype and it works as expected *mvn archetype:generate -DarchetypeGroupId=org.apache.camel.archetypes -DarchetypeArtifactId=camel-archetype-spring-boot -DarchetypeVersion=4.19.0-SNAPSHOT -DgroupId=com.test -DartifactId=test -Dversion=1.0-SNAPSHOT* Greetings, Federico Il giorno ven 27 feb 2026 alle ore 11:24 Bedürftig, Arne via users < [email protected]> ha scritto: > Hey all > > We use Apache Camel 4 in Spring Boot. So far, we have kept the > dependencies up to date. Latest apps are using 4.17.0. Just upgraded our > template to 4.18.0 and Spring Boot 3.5.10. We use Java 21. > > Based on the roadmap: > > > The next 4.19 release is planned in April. > > The goal of that release is to migrate to Spring Boot v4, however all > together there will be related work to be done in upcoming release to get > all of this aligned. > > I would like to ask for general guidance and ideas on the path to Spring > Boot 4.x. I understand that with Apache Camel 4.19.0 Spring Boot 4 support > will be added. How do we know individual dependencies will also work under > 4.19.0 and SB 4 (especially the Camel spring-boot-starters)? > > Thank you in advance. > > Regards, > Arne > > > Freundliche Grüße / Best regards > > > > i.A. Arne Bedürftig > > Integration Architect | Integration intern EAI (EAI) > > IT - Architecture & Integration (AI) > > > > CITTI Handelsgesellschaft mbH & Co. KG > > Mühlendamm 1 | 24113 Kiel | Deutschland > > Mobil: +49 151 65793604 > > www.citti.de<http://www.citti.de/> | www.chefsculinar.de< > http://www.chefsculinar.de/> | www.chefsculinar.com< > http://www.chefsculinar.com/> > > > > Kommanditgesellschaft: Amtsgericht Kiel HRA 858 KI | Komplementär: CITTI > Verwaltungsgesellschaft mbH > > Amtsgericht Kiel HRB 4417 | Gerichtstand: Kiel > > Geschäftsführer: Gerhard Lütje, Dirk Lütje, Christoph Langness, Dr. Frank > Scholz > > ------------------------------------------------------------------------------ > Informationen (einschließlich Pflichtangaben und Datenschutzerklärungen) > zu einzelnen, innerhalb der EU tätigen Gesellschaften und > Zweigniederlassungen der CITTI-Gruppe finden Sie unter > http://www.citti.de/html/pflichtangaben.html. Diese E-Mail enthält > vertrauliche und/ oder rechtlich geschützte Informationen. Wenn Sie nicht > der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, > informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. > Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist > nicht gestattet. > > Please refer to http://www.citti.de/html/pflichtangaben.html for > information (including mandatory corporate particulars and data protection > declarations) on selected CITTI branches and group companies registered or > incorporated in the European Union. This e-mail may contain confidential > and/or privileged information. If you are not the intended recipient (or > have received this e-mail in error) please notify the sender immediately > and delete this e-mail. Any unauthorized copying, disclosure or > distribution of the material in this e-mail is strictly forbidden. > > ------------------------------------------------------------------------------ >
