[ https://issues.apache.org/activemq/browse/CAMEL-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60153#action_60153 ]
Charles Moulliard commented on CAMEL-2830: ------------------------------------------ That means that we should create a specific error for that case to avoid that IllegalArgumentException (used for the moment) or FormatNumberException will be by passed. > camel-bindy - Add option to allow bindy to collect failed mapping so end > users can decide what to do > ---------------------------------------------------------------------------------------------------- > > Key: CAMEL-2830 > URL: https://issues.apache.org/activemq/browse/CAMEL-2830 > Project: Apache Camel > Issue Type: New Feature > Components: camel-bindy > Affects Versions: 2.3.0 > Reporter: Claus Ibsen > Priority: Minor > Fix For: Future > > > Suppose you are processing a big file with many CSV rows. > And you map those using bindy to objects. Now some of the CSV rows is > invalid, which would cause Bindy to thrown an exception. > We should add an option so end user can suppress this and let bindy continue > and collect those failed rows. > Then those rows could be set as a header on the message. > You may need some container object to store the validation errors, or offer a > interface for callbacks when a validation error was found. > For example like the {{org.xml.sax.ErrorHandler}} interface which is callback > based. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.