no further work.
> > > >
> > > > There should be a community of developers working on the beanio fork
> to
> > > > consider it again for being in Camel.
> > > >
> > > > Il mar 27 dic 2022, 21:39 kilidarria ha
> > scritto
rea Cosentino <
anco...@gmail.com> Date: 12/27/22 3:03 AM (GMT-08:00) To:
users@camel.apache.org Subject: Re: Camel 3.X / DataFormat BeanIO The
problem with this kind of dead libraries is related to the fact
thatthey
rapidly become affected by multiple CVEs.So being mature and non
mainta
a ha
> scritto:
> > >
> > >> I would vote to bring this back and maintaining it. We also have
> > numerous
> > >> flat files with complex record structures defined. We are currently RH
> > fuse
> > >> I'm not sure what their upgrade pla
gt; I would vote to bring this back and maintaining it. We also have
> numerous
> >> flat files with complex record structures defined. We are currently RH
> fuse
> >> I'm not sure what their upgrade plans are for Camel 3 so I have some
> >> time. MarciSent f
(GMT-08:00) To:
users@camel.apache.org Subject: Re: Camel 3.X / DataFormat BeanIO The
problem with this kind of dead libraries is related to the fact thatthey
rapidly become affected by multiple CVEs.So being mature and non
maintained, it's a problem.Since nobody updates or release new versions,
Subject: Re:
Camel 3.X / DataFormat BeanIO If you have time and there is a willing to
maintain the library, this isgoodAs of today, the only updated release is
milestone from 18 months ago andno further work.There should be a community of
developers working on the beanio fork toconsider it again
om my Galaxy
> Original message From: Andrea Cosentino <
> anco...@gmail.com> Date: 12/27/22 3:03 AM (GMT-08:00) To:
> users@camel.apache.org Subject: Re: Camel 3.X / DataFormat BeanIO The
> problem with this kind of dead libraries is related to the fact thatthey
> ra
: Andrea Cosentino
Date: 12/27/22 3:03 AM (GMT-08:00) To: users@camel.apache.org Subject: Re:
Camel 3.X / DataFormat BeanIO The problem with this kind of dead libraries is
related to the fact thatthey rapidly become affected by multiple CVEs.So being
mature and non maintained, it's a problem.Since
u/> <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 b
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
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
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
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
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
Hello.
It seems very strange to me to remove a component when no easy
alternative exists. Almost half of our about 100 projects use fixed
length files that are still used by many companies legacy systems, and
rely on beanio.
In my opinion, a stable component that has no recent change is not
Hi
BeanIO is a dead/not-active project and removed in 3.x, as some other
components - its documented in the upgrade guide to 3.17.x
On Tue, Dec 27, 2022 at 11:38 AM Ephemeris Lappis <
ephemeris.lap...@gmail.com> wrote:
> Hello.
>
> I'm very surprised to see that the data format BEANIO has been
Hello.
I'm very surprised to see that the data format BEANIO has been removed
in the last Camel versions. Isn't any replacement component ?
We used BeanIO in many exchanges that handle enterprise legacy systems
fixed length formatted files (big retail companies still use it for
many purposes). I
17 matches
Mail list logo
