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 <anco...@gmail.com> 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 back in the > camel > > codebase. > > > > Il giorno mar 27 dic 2022 alle ore 12:00 Ephemeris Lappis < > > ephemeris.lap...@gmail.com> ha scritto: > > > > > 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 > > > "dead", just "mature". > > > > > > Can we hope it gets back to a future Camel release ? > > > > > > Regards. > > > > > > Le mar. 27 déc. 2022 à 11:47, Claus Ibsen <claus.ib...@gmail.com> a > écrit > > > : > > > > > > > > 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 > 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 know alternative components for many file formats > > > > > (xml, csv, etc.), but for fixed length, BeanIO is really the only > one > > > > > that can handle complex structured files... > > > > > > > > > > What can we do :( ??? > > > > > > > > > > Thanks for any idea that can save our migration plans. > > > > > > > > > > Regards. > > > > > > > > > > > > > > > > > -- > > > > Claus Ibsen > > > > ----------------- > > > > @davsclaus > > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
