Hello.
Yes, some kind of process to select what component live or die is a good
idea. In the case of beanio, I'm almost sure that many IT teams still
use it for customers that need its features. Even if old fixed length
formats seem to be obsolete today, retail companies (and more) like our
Maybe we need a process to select components to be removed, with the
community feedback, and alert the developer that the component is
deprecated after a component is selected to be removed. I'm understanding
one problem here is the component was removed causing surprise to users.
On Tue, Dec
Sometimes it's also good to question why the project is dead. I also worked
for big retail companies, as well as government organizations, and saw
fixed length formats on various occasions. The truth is that these formats
are outdated and get less and less support, thus fewer libraries and tools.
Hello again.
I'd personally like to contribute to bring Beanio back to Camel, but in
the context of our customer's works I'm afraid we can't afford it : our
current job is essentially to create and maintain softwares and
information systems of these business entities, using middlewares and
Willingness is there, time is always the bugger. I'll review our release
schedule see when we might get to Camel 3. That will help set my priorities.
Sent from my Galaxy
Original message From: Andrea Cosentino
Date: 12/27/22 1:16 PM (GMT-08:00) To: users@camel.apache.org
If you have time and there is a willing to maintain the library, this is
good
As of today, the only updated release is milestone from 18 months ago and
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
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
from my Galaxy
Original message From:
Thank you, Claus, for this important caution but we didn't notice this in Camel
documentation.
We are newly developing our projects with Camel, and it is important for us to
use most promising ways.
Which DSL is most valuable for future use cases?
Is there any roadmap for Camel? I found some
Hello.
We also use bindy for delimited formats or fixed columns, but only with
rather simpler structures (homogeneous lines in most cases).
BeanIo mapping is richer to define several levels of groups and records,
and let's separate the format definition from the code, more or less the
same way
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
Hi
I have just fixed that to be !route so the WARN is only logged when no
custom id has been set.
On Mon, Dec 26, 2022 at 4:08 PM Claus Ibsen wrote:
> Hi
>
> Ah yeah it should be NOT custom id assigned.
> You are welcome to send a PR
>
> BTW is there a reason you turn off remove all
Hi
Just a caution that using camel-spring-xml with Spring XML is becoming
legacy/deprecated.
It is the very old XML DSL in Camel v1/v2.
So what you can do is to use a route as DLQ that uses direct where you can
then do
from direct myDLQ
log bla blah
to jms:dead
And then configure the
Hi,
Thank you for your reply...
Yes, I refer the inside errorHandler.
Do you mean that
org.apache.camel.spring.xml.handler.ErrorHandlerDefinitionParser.doParse should
parse ?
I checked your suggestions, but the first 2 parameters are related with the
redeliveryPolicy and our aim is to
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
Hi
If you refer to
As something that is supposed to be parsed by that spring code, then that
is not.
The is Log EIP and not really part of the error handler.
The following options is what configures how "verbose" the error handler is
when it executes and what it logs
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
After some investigation in Apache-Camel sources, we see that parser do not
parse log line in errorHandler section (see
https://github.com/apache/camel/blob/main/components/camel-spring-xml/src/main/java/org/apache/camel/spring/xml/handler/ErrorHandlerDefinitionParser.java#L77]
).
It seems it
22 matches
Mail list logo
