Re: You can only set routeId one time per route
I think you’re referring to this Jira issue:
https://issues.apache.org/jira/browse/CAMEL-13525
Why do you need to set/override the routeid multiple times for 1 route?
You could either:
* Dynamically build/remove your routes via a RouteBuilder where you have
control of setting that routeid just once (but still dynamically)
* Use other unique identifiers for that route (per example set a property
for the ‘customerid’ that triggers the specific route (or whatever the use-case
is).
Kind regards,
Maarten Donderwinkel
Senior Technical Consultant
From: Xilai Dai
Date: Monday, 1 November 2021 at 10:07
To: users@camel.apache.org
Subject: Re: You can only set routeId one time per route
ATTENTION: This email originated from outside of the organization.
Hi Claus,
It was allowed override it in Camel 2.x.
was there a Camel Jira for it?
Because the users using Camel 2 already created Routes with routeId() inside
anywhere.
Thanks.
From: Claus Ibsen
Sent: Monday, November 1, 2021 4:37 PM
To: users@camel.apache.org
Subject: Re: You can only set routeId one time per route
Warning! External email. Exercise caution when opening attachments or clicking
any links.
Yes a route should not change its id
On Mon, Nov 1, 2021 at 8:57 AM Xilai Dai wrote:
>
> Hi there,
>
> What's the good reason in Camel 3 the routeId() can be set only once?
>
> public RouteDefinition routeId(String id) {
> if (hasCustomIdAssigned()) {
> throw new IllegalArgumentException("You can only set routeId one
> time per route.");
> }
> setId(id);
> return this;
> }
>
> is there a Camel Jira for it?
>
> Thanks!
>
> As a recipient of an email from Talend, your contact personal data will be on
> our systems. Please see our privacy notice (updated August 2020) at Talend,
> Inc. <https://www.talend.com/contacts-privacy-policy/>
>
>
--
Claus Ibsen
-
https://urldefense.com/v3/__http://davsclaus.com__;!!CiXD_PY!C6T30Kv7TOpwCeCMZtbpZUUp-zp25uxig22TmcmuoiJMoor5JxOKO5wZ3H4c$<https://urldefense.com/v3/__http:/davsclaus.com__;!!CiXD_PY!C6T30Kv7TOpwCeCMZtbpZUUp-zp25uxig22TmcmuoiJMoor5JxOKO5wZ3H4c$>
@davsclaus
Camel in Action 2:
https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!CiXD_PY!C6T30Kv7TOpwCeCMZtbpZUUp-zp25uxig22TmcmuoiJMoor5JxOKO6QhtIzg$<https://urldefense.com/v3/__https:/www.manning.com/ibsen2__;!!CiXD_PY!C6T30Kv7TOpwCeCMZtbpZUUp-zp25uxig22TmcmuoiJMoor5JxOKO6QhtIzg$>
As a recipient of an email from Talend, your contact personal data will be on
our systems. Please see our privacy notice (updated August 2020) at Talend,
Inc. <https://www.talend.com/contacts-privacy-policy/>
Re: Building Apache Camel
The MaxPermSize option has been deleted as of Java 17 (in Java 16 this is marked as obsolete). You should either remove it or change it to MaxMetaspaceSize. According to the Java Docs: -XX:MaxPermSize=size Sets the maximum permanent generation space size (in bytes). This option was deprecated in JDK 8 and superseded by the -XX:MaxMetaspaceSize option. https://docs.oracle.com/en/java/javase/17/docs/specs/man/java.html#removed-java-options Met vriendelijke groet | Kind Regards | Meilleures salutations | Mit freundlichen Grü?en, Maarten Donderwinkel Aiden www.aiden.eu [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUzUExURQAAAEBQgDhQeDpQejxQeDlTeTpSeDtSeTpSeDtSeTtSejxSeTtReTtTeTtSeTtSeTtSeaJ0QfYQdFJOUwAQIDBAUGBwgI+fr7/P3+8jGoKKCXBIWXMAABcRAAAXEQHKJvM/oUlEQVQ4T6WSWw7DIAwE7VACtDRw/9MW7C1Kw0OKOl+wI0C2ob9hb7AaYXPesexgT26uXznOdbl2oUsOvSE5I7bqxEjO1JtFj44Sq00P7C88xXrsrmxi06xdenim+VhqI3aqURV0V7c+rZpT19TYtCHf9Zzf0O6IC10Y6TLnL6KvnQ2Qqh3Sxg4pA+3nadrjAckvVkuLo59QYevD8IvdgegD6EkL94fs/OQASUVORK5CYII=] +31 (0) 88 060 5111 Locatie Boxtel Kastanjelaan 3 | 5283 WE Boxtel [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUzUExURQAAAEBQgDhQeDpQejxQeDlTeTpSeDtSeTpSeDtSeTtSejxSeTtReTtTeTtSeTtSeTtSeaJ0QfYQdFJOUwAQIDBAUGBwgI+fr7/P3+8jGoKKCXBIWXMAABcRAAAXEQHKJvM/oUlEQVQ4T6WSWw7DIAwE7VACtDRw/9MW7C1Kw0OKOl+wI0C2ob9hb7AaYXPesexgT26uXznOdbl2oUsOvSE5I7bqxEjO1JtFj44Sq00P7C88xXrsrmxi06xdenim+VhqI3aqURV0V7c+rZpT19TYtCHf9Zzf0O6IC10Y6TLnL6KvnQ2Qqh3Sxg4pA+3nadrjAckvVkuLo59QYevD8IvdgegD6EkL94fs/OQASUVORK5CYII=] +31 (0) 88 060 5103 Contact E-mail: maarten.donderwin...@aiden.eu [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUhUExURQAAAEBQgDpSeDtSeTpSeDtSejtReTtTeTtSeTtSeTtSeSPg/l8KdFJOUwAQYHCAn7/P3+9H8icYCXBIWXMAABcRAAAXEQHKJvM/TElEQVQ4T+3Myw6AMAhE0Skgtf7/B6vpNGVBfOx7VmRuAj5Rj5Tr4MelmVq7D+c69CoiNa/7lNTCCyirrhq81TolNfpXjU+7jesT4AQwOwYrLtoZpwBJRU5ErkJggg==] +31 (0) 6 8683 0832 [cid:afbeelding1_eb30b6f7-44ba-411f-af30-95d95824f737.png]<https://www.facebook.com/weareAiden.eu> [cid:afbeelding2_ae36edb4-28f1-4ddd-b314-097daeb787bd.png] <https://www.linkedin.com/company/aiden-eu/> [cid:afbeelding3_88fd1a9e-f670-41ca-b591-7b87eb136bfe.png] <https://twitter.com/weareAiden> [cid:afbeelding4_53e3956d-90a9-4883-9fc2-fac4ed0659da.png] <https://www.youtube.com/channel/UCcLccRfot11DrZLNhlAS8fA> [cid:aidenlogowithstrapline_royalblue_cmyk_9d2ff840-c0a7-46c9-b176-e08fc6dd5956.png] <https://www.aiden.eu/> <https://www.twitter.com/user_name_here> <https://www.youtube.com/user/user_name_here> From: ski n Date: Tuesday, 20 September 2022 at 10:35 To: users@camel.apache.org Subject: Re: Building Apache Camel You can either build with OpenJDK 11 with the option or build it with OpenJDK 17 without the option. The option: -XX:MaxPermSize=size Was already deprecated for a while and has been removed in Java 17. Raymond On Tue, Sep 20, 2022 at 10:27 AM FÖRSTERLING Björn < bjoern.foersterl...@cpb-software.com> wrote: > Hello, > > I just tried building Apache Camel to get a jar. > According to the documentation you have to execute these two lines: > > $ export MAVEN_OPTS="-Xms3000m -Xmx3000m -XX:MaxPermSize=512m" > $ mvn clean source:jar install -Pfastinstall > Unrecognized VM option 'MaxPermSize=512m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > > I use openjdk version "17.0.4" 2022-07-19. > > Do I need an older java version or is the MaxPermSize option different > different in java 17? > > Thanks in advance. > > Greetings > Björn Försterling >
Re: Camel 3.X / DataFormat BeanIO
For fixed length projects I’ve used camel-bindy in the past https://camel.apache.org/components/3.18.x/dataformats/bindy-dataformat.html#_4_fixedlengthrecord I don’t know if this component suits your use case as I’ve never used BeanIO, but given that you refer to fixedlength records I hope it can serve as an alternative. Met vriendelijke groet | Kind Regards | Meilleures salutations | Mit freundlichen Grüßen, Maarten Donderwinkel Aiden www.aiden.eu [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUzUExURQAAAEBQgDhQeDpQejxQeDlTeTpSeDtSeTpSeDtSeTtSejxSeTtReTtTeTtSeTtSeTtSeaJ0QfYQdFJOUwAQIDBAUGBwgI+fr7/P3+8jGoKKCXBIWXMAABcRAAAXEQHKJvM/oUlEQVQ4T6WSWw7DIAwE7VACtDRw/9MW7C1Kw0OKOl+wI0C2ob9hb7AaYXPesexgT26uXznOdbl2oUsOvSE5I7bqxEjO1JtFj44Sq00P7C88xXrsrmxi06xdenim+VhqI3aqURV0V7c+rZpT19TYtCHf9Zzf0O6IC10Y6TLnL6KvnQ2Qqh3Sxg4pA+3nadrjAckvVkuLo59QYevD8IvdgegD6EkL94fs/OQASUVORK5CYII=] +31 (0) 88 060 5111 Locatie Boxtel Kastanjelaan 3 | 5283 WE Boxtel [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUzUExURQAAAEBQgDhQeDpQejxQeDlTeTpSeDtSeTpSeDtSeTtSejxSeTtReTtTeTtSeTtSeTtSeaJ0QfYQdFJOUwAQIDBAUGBwgI+fr7/P3+8jGoKKCXBIWXMAABcRAAAXEQHKJvM/oUlEQVQ4T6WSWw7DIAwE7VACtDRw/9MW7C1Kw0OKOl+wI0C2ob9hb7AaYXPesexgT26uXznOdbl2oUsOvSE5I7bqxEjO1JtFj44Sq00P7C88xXrsrmxi06xdenim+VhqI3aqURV0V7c+rZpT19TYtCHf9Zzf0O6IC10Y6TLnL6KvnQ2Qqh3Sxg4pA+3nadrjAckvVkuLo59QYevD8IvdgegD6EkL94fs/OQASUVORK5CYII=] +31 (0) 88 060 5103 Contact E-mail: maarten.donderwin...@aiden.eu [data:image/png;base64,iVBORw0KGgoNSUhEUgAAAB0dCAMAAABhTZc9AXNSR0IArs4c6QRnQU1BAACxjwv8YQUhUExURQAAAEBQgDpSeDtSeTpSeDtSejtReTtTeTtSeTtSeTtSeSPg/l8KdFJOUwAQYHCAn7/P3+9H8icYCXBIWXMAABcRAAAXEQHKJvM/TElEQVQ4T+3Myw6AMAhE0Skgtf7/B6vpNGVBfOx7VmRuAj5Rj5Tr4MelmVq7D+c69CoiNa/7lNTCCyirrhq81TolNfpXjU+7jesT4AQwOwYrLtoZpwBJRU5ErkJggg==] +31 (0) 6 8683 0832 [cid:afbeelding1_eb30b6f7-44ba-411f-af30-95d95824f737.png]<https://www.facebook.com/weareAiden.eu> [cid:afbeelding2_ae36edb4-28f1-4ddd-b314-097daeb787bd.png] <https://www.linkedin.com/company/aiden-eu/> [cid:afbeelding3_88fd1a9e-f670-41ca-b591-7b87eb136bfe.png] <https://twitter.com/weareAiden> [cid:afbeelding4_53e3956d-90a9-4883-9fc2-fac4ed0659da.png] <https://www.youtube.com/channel/UCcLccRfot11DrZLNhlAS8fA> [cid:aidenlogowithstrapline_royalblue_cmyk_9d2ff840-c0a7-46c9-b176-e08fc6dd5956.png] <https://www.aiden.eu/> <https://www.twitter.com/user_name_here> <https://www.youtube.com/user/user_name_here> From: Claus Ibsen Date: Tuesday, 27 December 2022 at 12:30 To: users@camel.apache.org Subject: Re: Camel 3.X / DataFormat BeanIO And only if beanio become active again and do new releases we can consider adding it back. There is a 3.0 M1 release but its 1.5 years old, and only a few commits since that time. You can reach out to beanio on github and see if the maintainer can become active again, or you can ask if you can help out the project and make v3 a GA release and active maintained so it can come back into Camel. Yes I think a great flat file/csv/kvp project is very usable but it's sadly hard to do in open source as nobody sponsors such projects. On Tue, Dec 27, 2022 at 12:26 PM Claus Ibsen wrote: > Hi > > Yes you can take the old code and build it is a custom component and use > with camel > > On Tue, Dec 27, 2022 at 12:20 PM Ephemeris Lappis < > ephemeris.lap...@gmail.com> wrote: > >> Hello. >> >> I do agree about CVEs, that are also an important concern in our jobs, >> and I also know the price of maintaining complex systems with many >> components from many origins. And Camel is exactly this kind of >> system, built upon hundreds of components that make it a quite rich >> integration platform for enterprises that use both the most recent >> cloud aware applications, and very old file formats or protocols... >> >> Well, is there any way to integrate the "old" beanio component "our >> way" as a custom data format, and thus a solution not to stop our >> migration plan right now ? >> >> Thanks again. >> >> Regards. >> >> >> Le mar. 27 déc. 2022 à 12:03, Andrea Cosentino a >> écrit : >> > >> > The problem with this kind of dead libraries is related to the fact that >> > they rapidly become affected by multiple CVEs. >> > >> > So being mature and non maintained, it's a problem. >> > >> > Since nobody updates or release new versions, going ahead we're going to >> > include weak libraries if we maintain them in codebase. >> > >> > So, I don't think there is any hope to see the component
