AW: Deadletter and Aggregation again

Thats is the hard method. And I am shy to use plain programming in a framework. Regarding split: the problem is that is not a simple spilt. 1. Zip is splitted to XML, TIFF0, TIFF1, 2. XML is splitted to DATA0, DATA1, And TIFF0 and DATA0, (TIFF1, DATA1), ... is combined then. So

AW: Deadletter and Aggregation again

>The aggregator is a 2 phased EIP so what comes out of the aggregator is not >tied to the input. That is by design. Is there a way to prevent or control the transation, when original input (file) is deleted/moved? -Ursprüngliche Nachricht- Von: Claus Ibsen Gesendet: Montag, 6.

Deadletter and Aggregation again

Hi, to be able to save the original message to dead letter directory even in multiple nested splits I store it at a property. .process(exchange -> { final Message orgMessage = exchange.getUnitOfWork().getOriginalInMessage();

ExchangeHelper::getOriginalInMessage

Hi, looking at ExchangeHelper::getOriginalInMessage in case of exceptionhandling and useOriginalMessage() it seems that only the direct parent is used. But the original input (GenericFileMessage) is parent of parent of parent. I could patch the getOriginalInMessage in that way it goes through

useOriginalMessage at parallelProcessing

Hi, I still fiddling around with deadletter handling. I got a zip. This is splitted. When there is an error an exception is thrown. Then error handler (and the route) shall write the original file to dead letter dir. This works when I comment out the parallelProcessing. With

AW: Aggregation and unitOfWork

Hi, I tried to. But the messages I get in aggregate(old, new) or different and don’t have the information anymore. And the aggregate-method with three params is never called. @Override public Exchange aggregate(Exchange oldExchange, Exchange newExchange, Exchange inputExchange) {

Aggregation and unitOfWork

Hi, Aggration seems to lost the connection to original Message. I have the following construct: from(FILE_IN_URI) .split(new ZipSplitter()).shareUnitOfWork() .streaming() .choice() .when(simple("${in.header.CamelFileName} ends with 'xml'"))

AW: DefaultComponent

I have it. Its flowable that uses 2-style DefaultComponent etc. -Ursprüngliche Nachricht- Von: Claus Ibsen Gesendet: Dienstag, 3. Dezember 2019 13:44 An: users@camel.apache.org Betreff: Re: DefaultComponent Hi Oh didnt know so much about flowable-camel as its 3rd party and not ASF.

AW: DefaultComponent

Its not my components. Its spring boot or flowable. But I cannot see in dependeny tree where flowble-camel uses camel-core or camel-support. When I patch the classes DefaultComponent /-Consumer etc. it works. -Ursprüngliche Nachricht- Von: Claus Ibsen Gesendet: Dienstag, 3.

AW: DefaultComponent

Yes. I know and my own components use this. But it seems spring or flowable needs this class there. -Ursprüngliche Nachricht- Von: Andrea Cosentino Gesendet: Dienstag, 3. Dezember 2019 13:01 An: users@camel.apache.org Cc: dev Betreff: Re: DefaultComponent In Camel 3 the

DefaultComponent

Hi, I got this error. What is missing? java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent Stacktrace: java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent at java.base/java.lang.ClassLoader.defineClass1(Native Method) ~[na:na] at

AW: [ANNOUNCEMENT] Apache Camel 3.0.0 Released

A. Thanks. Didn't expect this from 3.0.0-RC3 to 3.0.0 -Ursprüngliche Nachricht- Von: Andrea Cosentino Gesendet: Montag, 2. Dezember 2019 15:25 An: users@camel.apache.org Cc: dev Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released The groupId of the starters has been changed

AW: [ANNOUNCEMENT] Apache Camel 3.0.0 Released

Hi, But camel-spring-boot-starter is still 3.0.0-RC3 ? -Ursprüngliche Nachricht- Von: Grzegorz Grzybek Gesendet: Freitag, 29. November 2019 15:37 An: users@camel.apache.org Cc: d...@camel.apache.org Betreff: Re: [ANNOUNCEMENT] Apache Camel 3.0.0 Released Congratulations! Time to

parse HTML Email

Hi, is there a build in way to parse HTML and RTF Emails. I simply need a plain text. Only what I found was to unmarshall into different message-part. Thomas

AW: NoClassDefFoundError: DefaultComponent 3.0.0-RC1

Actually that is what I suppose. Or camel - 3.0.0 is buggy.  -Ursprüngliche Nachricht- Von: Andrea Cosentino Gesendet: Mittwoch, 2. Oktober 2019 15:00 An: users@camel.apache.org Betreff: Re: NoClassDefFoundError: DefaultComponent 3.0.0-RC1 If you are moving to camel 3 probably you

AW: NoClassDefFoundError: DefaultComponent 3.0.0-RC1

Hi I thought I did this. I use this. Snipped. I suspect someone else, may be from spring, uses this *at rumtime*. Its not a compile error. --- import java.util.Map; import org.apache.camel.Endpoint; import org.apache.camel.support.DefaultComponent; import

NoClassDefFoundError: DefaultComponent 3.0.0-RC1

Hello I get this error when upgrading to 3.0.0-RC1 As far as I noticed DefaultComponent moved to support instead of impl. Who wants org/apache/camel/impl/DefaultComponent? Thomas java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent at

AW: Email to dead letter channel

Thank you, Giovanni. This works. Maybe you can give me a hint how to deal with the same approach when splitting. Pseudocode errorHandler(deadLetterChannel(String.format("file://dead")).useOriginalMessage()); from (in).split() .choice() .when (type == 0)

AW: Email to dead letter channel

No. The body is not stored as it come. But text only. Without formatting (e.g. RTF). I simply want to backup the original Email as eml in case of error. -Ursprüngliche Nachricht- Von: Condello, Giovanni Gesendet: Donnerstag, 19. September 2019 15:47 An: users@camel.apache.org Betreff:

AW: own endpoint exmaple?

Thanks. Will look at it. -Ursprüngliche Nachricht- Von: Condello, Giovanni Gesendet: Donnerstag, 19. September 2019 13:55 An: users@camel.apache.org Betreff: Re: own endpoint exmaple? A couple of suggestions from someone that had to build a custom component: - Use the archetype to

AW: own endpoint exmaple?

Simply hide a complex monitoring (db-entries, log, etc.) with a simple call like "file://" "log:". I could use a bean or processor and I actually I had, but I thought its simplier so. For the caller (routedef) and for clean code. -Ursprüngliche Nachricht- Von: Omar Al-Safi Gesendet:

Email to dead letter channel

Hi, I send an email with formatting, html or rtf and a pdf as attachment. But in the dead letter file there is only plain text. How can I save the orginal email in case of exception? Code so far in configure(): errorHandler(deadLetterChannel(String.format("file://%s",

AW: own endpoint exmaple?

"Scaffolding your component through maven archetype" I think at the moment I didn’t know much about it. I really didn’t want to blow up pom only for a little endpoint. Or did I not get it? -Ursprüngliche Nachricht- Von: Alex Dettinger Gesendet: Donnerstag, 19. September 2019 10:20

AW: own endpoint exmaple?

Hi, thanks so far. I didn’t know that I had to explicitely create a Component. The direct example helped a lot. But there is this contruct, and it will not work with my code. name is not set. (it has getter and setter) I want that name is "thomas" when route-def is like

AW: own endpoint exmaple?

Hi, the problem is that a lot of links on the page you are mentionend, are dead ("page not found"). I should have told that in the first posting. I use spring so I hoped spring will find it. I will look at the examples. Thanks. -Ursprüngliche Nachricht- Von: Omar Al-Safi Gesendet:

AW: own endpoint exmaple?

Hi Alex, 1. I found this webpage but the links (e.g. createProducer()) goes to "page not found". 2. Stupid question: how and where to do this? -Ursprüngliche Nachricht- Von: Alex Dettinger Gesendet: Montag, 16. September 2019 12:52 An: users@camel.apache.org Betreff: Re: own

own endpoint exmaple?

Hi, can some point me to a working example where an own endpoint was created. In route I say: .to("thomas://foo") my Endpoint is @Component @UriEndpoint(scheme = "thomas", title = "Thiele", syntax="thomas:name", label = "Thomas") public class ThomasStep extends DefaultEndpoint {} But I