Re: Camel 4 migration blog post - Feedback welcome
On Fri, Oct 6, 2023 at 4:08 PM Mark Nuttall 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 > > Oh is this a default change in Kafka itself (eg upgrade of kafka-client) or something thay may have changed in Camel 3 -> 4. We can add a note about this in the 4.0 migration guide. You are welcome to send a PR. > On Fri, Oct 6, 2023 at 3:49 AM Claus Ibsen 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 > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4 migration blog post - Feedback welcome
Hi Raymon Yes these are good observations about "why upgrade to v4 and what benefits do I get". Maybe we can write a blog post about this, and you are surely welcome to help with this. A blog post is just to do a PR for camel-website (you can copy an existing blog post). And then send as draft PR, then others can easily review and help with sending updates etc. On Fri, Oct 6, 2023 at 4:24 PM ski n wrote: > 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 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 > 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 > > > > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4 migration blog post - Feedback welcome
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 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 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 > > >
Re: Camel 4 migration blog post - Feedback welcome
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 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 >
Re: Camel 4 migration blog post - Feedback welcome
On Fri, Oct 6, 2023 at 11:34 AM Mikael Koskinen wrote: > Hi, > > For me the biggest issues regarding Camel 4 have been when Karavan VS Code > extension updated itself to 4.0.0. I'm not sure things related to Karavan > are discussed in the blog post but here's couple things we've encountered. > > In short, if you use Karavan 4.x.x to open a route which has been designed > with the 3.x.x version, in many cases the route breaks as the designer > removes parts of it. I think the yaml schema has changed a bit between the > releases and the editor only supports the latest version with no backward > compatibility. In addition to that, the latest Karavan editor has some > issues UI issues (scrolling the property panel doesn't work as it should, > some textboxes are broken). We decided to downgrade the Karavan back to > 3.x.x even though we updated Camel to 4.x.x. > > You should generally use the Karavan release that is released for a given Camel version, eg 3.21 for 3.21 and so on. Having a single continued release of Karavan (and any Camel tooling for the matter) is hard to have it support many older versions going back. And also Karavan is in heavy development and Camel v4 is going to be where it will be ready for mass adoption. > The Camel 4 itself has been a rock solid release. No issues. > pe 6. lokak. 2023 klo 11.52 ski n (raymondmees...@gmail.com) kirjoitti: > > > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. > > > > Currently, thus not migrating yet, but planning has started. > > > > The things I need to consider: > > > > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently > > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation > still > > available? Like to compare sometimes. > > - Jakarta stuff in my own code/dependencies. > > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ > > Classic (embedded) server doesn't support it yet. > > - Deprecated components: I use the following components: > > > > camel-atlasmap > > camel-directvm > > camel-elasticsearch-rest > > camel-rabbitmq > > camel-rest-swagger > > camel-websocket > > camel-vm > > > > So I need to change these dependencies and some code here > > > > - I use extendedCamelContext a lot, so need to check the API changes out. > > For example use the PluginHelper instead of the extendedCamelContext > > - Update SLFJ to version 2.0 > > > > Will let you know if I'm running into any issues. > > > > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( > > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a > > recipe to move to Camel 4 then it would be probably easier to do the > > migration. > > > > Raymond > > > > > > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen > 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 > > > > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4 migration blog post - Feedback welcome
Hi Raymond Thanks for the feedback. Yes you are not the typical Camel end user, so your migration "work" is more than normal. The note about using PluginHelper etc is something we should highlight in the blog post, thanks. On Fri, Oct 6, 2023 at 10:52 AM ski n wrote: > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. > > Currently, thus not migrating yet, but planning has started. > > The things I need to consider: > > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation still > available? Like to compare sometimes. > - Jakarta stuff in my own code/dependencies. > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ > Classic (embedded) server doesn't support it yet. > - Deprecated components: I use the following components: > > camel-atlasmap > camel-directvm > camel-elasticsearch-rest > camel-rabbitmq > camel-rest-swagger > camel-websocket > camel-vm > > So I need to change these dependencies and some code here > > - I use extendedCamelContext a lot, so need to check the API changes out. > For example use the PluginHelper instead of the extendedCamelContext > - Update SLFJ to version 2.0 > > Will let you know if I'm running into any issues. > > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a > recipe to move to Camel 4 then it would be probably easier to do the > migration. > > Raymond > > > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen 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 > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel 4 migration blog post - Feedback welcome
The reason for camel-atlasmap to be removed was the fact Atlasmap was discontinued. There were no releases since October. Il giorno ven 6 ott 2023 alle ore 11:34 Gerald Kallas ha scritto: > Hi folks, > > what's the reason that camel-atlasmap has been removed in Camel 4. Is > there any alternative planned for mapping processors that don't need to be > coded? > > Best > Gerald > > > ski n hat am 06.10.2023 10:51 CEST > geschrieben: > > > > > > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. > > > > Currently, thus not migrating yet, but planning has started. > > > > The things I need to consider: > > > > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently > > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation > still > > available? Like to compare sometimes. > > - Jakarta stuff in my own code/dependencies. > > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ > > Classic (embedded) server doesn't support it yet. > > - Deprecated components: I use the following components: > > > > camel-atlasmap > > camel-directvm > > camel-elasticsearch-rest > > camel-rabbitmq > > camel-rest-swagger > > camel-websocket > > camel-vm > > > > So I need to change these dependencies and some code here > > > > - I use extendedCamelContext a lot, so need to check the API changes out. > > For example use the PluginHelper instead of the extendedCamelContext > > - Update SLFJ to version 2.0 > > > > Will let you know if I'm running into any issues. > > > > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( > > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a > > recipe to move to Camel 4 then it would be probably easier to do the > > migration. > > > > Raymond > > > > > > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen > 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 > > > >
Re: Camel 4 migration blog post - Feedback welcome
Hi, For me the biggest issues regarding Camel 4 have been when Karavan VS Code extension updated itself to 4.0.0. I'm not sure things related to Karavan are discussed in the blog post but here's couple things we've encountered. In short, if you use Karavan 4.x.x to open a route which has been designed with the 3.x.x version, in many cases the route breaks as the designer removes parts of it. I think the yaml schema has changed a bit between the releases and the editor only supports the latest version with no backward compatibility. In addition to that, the latest Karavan editor has some issues UI issues (scrolling the property panel doesn't work as it should, some textboxes are broken). We decided to downgrade the Karavan back to 3.x.x even though we updated Camel to 4.x.x. The Camel 4 itself has been a rock solid release. No issues. pe 6. lokak. 2023 klo 11.52 ski n (raymondmees...@gmail.com) kirjoitti: > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. > > Currently, thus not migrating yet, but planning has started. > > The things I need to consider: > > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation still > available? Like to compare sometimes. > - Jakarta stuff in my own code/dependencies. > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ > Classic (embedded) server doesn't support it yet. > - Deprecated components: I use the following components: > > camel-atlasmap > camel-directvm > camel-elasticsearch-rest > camel-rabbitmq > camel-rest-swagger > camel-websocket > camel-vm > > So I need to change these dependencies and some code here > > - I use extendedCamelContext a lot, so need to check the API changes out. > For example use the PluginHelper instead of the extendedCamelContext > - Update SLFJ to version 2.0 > > Will let you know if I'm running into any issues. > > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a > recipe to move to Camel 4 then it would be probably easier to do the > migration. > > Raymond > > > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen 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 > > >
Re: Camel 4 migration blog post - Feedback welcome
Hi folks, what's the reason that camel-atlasmap has been removed in Camel 4. Is there any alternative planned for mapping processors that don't need to be coded? Best Gerald > ski n hat am 06.10.2023 10:51 CEST geschrieben: > > > Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. > > Currently, thus not migrating yet, but planning has started. > > The things I need to consider: > > - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently > the docs for 2.0 are gone, is the archive to Camel 2.0 documentation still > available? Like to compare sometimes. > - Jakarta stuff in my own code/dependencies. > - Jakarta stuff in other libraries (then Camel). For example ActiveMQ > Classic (embedded) server doesn't support it yet. > - Deprecated components: I use the following components: > > camel-atlasmap > camel-directvm > camel-elasticsearch-rest > camel-rabbitmq > camel-rest-swagger > camel-websocket > camel-vm > > So I need to change these dependencies and some code here > > - I use extendedCamelContext a lot, so need to check the API changes out. > For example use the PluginHelper instead of the extendedCamelContext > - Update SLFJ to version 2.0 > > Will let you know if I'm running into any issues. > > I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( > https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a > recipe to move to Camel 4 then it would be probably easier to do the > migration. > > Raymond > > > On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen 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 > >
Re: Camel 4 migration blog post - Feedback welcome
Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x. Currently, thus not migrating yet, but planning has started. The things I need to consider: - I first need to finish some stuff to upgrade from 2.x to 3.x (Currently the docs for 2.0 are gone, is the archive to Camel 2.0 documentation still available? Like to compare sometimes. - Jakarta stuff in my own code/dependencies. - Jakarta stuff in other libraries (then Camel). For example ActiveMQ Classic (embedded) server doesn't support it yet. - Deprecated components: I use the following components: camel-atlasmap camel-directvm camel-elasticsearch-rest camel-rabbitmq camel-rest-swagger camel-websocket camel-vm So I need to change these dependencies and some code here - I use extendedCamelContext a lot, so need to check the API changes out. For example use the PluginHelper instead of the extendedCamelContext - Update SLFJ to version 2.0 Will let you know if I'm running into any issues. I'm planning to use OpenRewrite to update to Spring Boot 3/Jakarta ( https://docs.openrewrite.org/recipes/java/spring/boot3). If there was a recipe to move to Camel 4 then it would be probably easier to do the migration. Raymond On Fri, Oct 6, 2023 at 9:49 AM Claus Ibsen 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 >
Camel 4 migration blog post - Feedback welcome
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
