Re: File consumer exchange fails when async/fire-forget SEDA subroute fails

2017-06-29 Thread souciance
What is it exactly that fails? I don't see anywhere in your code where you invoke a processor? Where exactly does the exception occur? On Thu, Jun 29, 2017 at 12:18 AM, craig.w [via Camel] < ml+s465427n5805390...@n5.nabble.com> wrote: > Hello all, > > I have 2 routes: > * a file consumer route: t

Re: File Consumer Exchange

2016-06-03 Thread Brad Johnson
Yeah, as Hans points out the "noop" will leave the file and not even create an exchange so you don't have to filter for it downstream. If you are polling you can set an idempotent flag on the file reader to ensure that it doesn't re-read a file it has already processed. On Fri, Jun 3, 2016 at 1:0

RE: File Consumer Exchange

2016-06-02 Thread Hans Orbaan
Hi, You can use the "no operation" functionality. See noop=true @ http://camel.apache.org/file2.html -Oorspronkelijk bericht- Van: bwest [mailto:bwesterfi...@gmail.com] Verzonden: Friday 3 June 2016 1:19 Aan: users@camel.apache.org Onderwerp: File Consumer Exchange Can I ignore an exc