Not being the typical Camel user, I see that as a compliment :) For the blog it may be also good to highlight not just how to upgrade (migration path), but also why to upgrade.
There are technical reason like being up to date with Jakarta EE/Spring/Quarkus, but I think most users are even more interested in the functional improvements of the framework. Some technical and functional improvements were highlighted here: https://camel.apache.org/blog/2023/08/camel4-whatsnew/ But some improvements are already refined in the coming 4.1 release, think of - Better support for Yaml DSL - Better support for XML DSL (xml-io improvements) - Better Kafka support (camel-kafka) - Jbang improvements - Better OpenTelemetry support - Improvements in dumping of routes Most Camel developers (at least here on the mailing list) are probably eager to migrate, but we also need to sell it to our colleagues or customers. The whole Jakarta thing says nothing to them, but better observability and better performance (like https://camel.apache.org/blog/2023/05/camel-4-performance-improvements/) is much better to communicate. Raymond On Fri, Oct 6, 2023 at 4:08 PM Mark Nuttall <mknutt...@gmail.com> wrote: > one thing that got us was, since we were using kafka with security but not > using Kafka idempotency, we had to add the following flag. As usual, kafka > messages were not helpful. > > camel.component.kafka.enable-idempotence=false > > On Fri, Oct 6, 2023 at 3:49 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > Hi > > > > If you have been migrating to Camel 4 already, then any feedback is > > welcome. > > > > You can comment in the PR, or post here in the mailing list > > https://github.com/apache/camel-website/pull/1071 > > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > >
