On Sun, Sep 9, 2012 at 4:09 PM, Tim Dudgeon tdudgeon...@gmail.com wrote:
I've got a route that splits a large file into records, using a splitter.
Its basically working but I can't get it to tolerate errors during the
splitting. The route terminates on the first error, but I want that error to
On 10/09/2012 07:04, Claus Ibsen wrote:
Where from is the IOException being thrown
From within the next() method of the Iterator that the splitter generates.
Tim
On Mon, Sep 10, 2012 at 8:36 AM, Tim Dudgeon tdudgeon...@gmail.com wrote:
On 10/09/2012 07:04, Claus Ibsen wrote:
Where from is the IOException being thrown
From within the next() method of the Iterator that the splitter generates.
Yeah the expression is not intended to throw exceptions,
I've got a route that splits a large file into records, using a splitter.
Its basically working but I can't get it to tolerate errors during the
splitting. The route terminates on the first error, but I want that
error to be caught so that the bad record can be logged and processing
continue
Which version of Camel do you use [1]?
Checkout [2] - stopOnException how to continue if an exception occurs (use
a custom AggregationStrategy).
And because it's a custom splitter, you have the full control how to handle
the error...
[1] http://camel.apache.org/how-can-i-get-help.html
[2]
Hi,
I'm using 2.10 version.
Yes, its a custom splitter so I could handle the exception. But not sure
what I would do with it, or whethr that is really a good thing to do.
stopOnException seems to relate to exceptions that occur downstream of
the splitter, not from the splitting itself?
And
