A good idea is to look at the unit tests of camel-beanio and how it tests this functionality.
On Tue, Aug 30, 2016 at 10:35 PM, spurcell <scott_purc...@mastercard.com> wrote: > Hello Brad, > > We have a large project in which we are taking in large csv files. Our team > wants to create a custom BeanReaderErrorHandler (from: > http://camel.apache.org/beanio.html) so we could convert errors to our > return errors and build return files for our customers in our newly created > application. > > If we let the Runtime errors go up the stack, it appears we lose some > information that our developers wanted to get from the BeanReaderException > such as getLineNumber(), getFieldText() etc. > > This camel is new to me, and I am struggling trying to implement the > BeanReaderErrorHandler interface > (http://beanio.org/2.1/docs/reference/index.html#BeanReaderErrorHandler) > from BeanIO and somehow configure that into the Camel route. > > Thank > Scott > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-BeanIODataFormat-Configure-ErrorHandler-for-BeanIO-Reader-tp5787005p5787013.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
