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.