You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/02/17 07:58:11 UTC
[jira] [Resolved] (CAMEL-2830) camel-bindy - Add option to allow
bindy to collect failed mapping so end users can decide what to do
[ https://issues.apache.org/jira/browse/CAMEL-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2830.
--------------------------------
Resolution: Unresolved
> 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/jira/browse/CAMEL-2830
> Project: 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 was sent by Atlassian JIRA
(v6.3.4#6332)