Norbert Becker

Ok - I found the reason for the behavior and created ticket https://sourceforge.net/p/opencsv/feature-requests/142/ You may think that it makes no sense to do such a coding. But that's how it looked liked before and worked with older versions of OpenCSV. So for me not really a bug, but some changes in implementation that may force users to adapt there code. Thanks again for your support! We are now happy (again) with OpenCSV in version 5.3 ;-).

Usage of CsvToBean.getCapturedExceptions() changed

Hi Andrew & Scott, thanks for the swift reply! Regarding syntax handling aligned to RFC4180: Ok - that's understandable and acceptable :-). The main problem had been that I got no error and the lines where just skipped. I checked our error handling: We use CsvToBean.setThrowExceptions(false) and retrieve the list of exceptions by CsvToBean.getCapturedExceptions() after parsing has finished. This list is still empty?! I changed the code and now use CsvToBean.setErrorHandler() to collect the exceptions....

Hi, we have been using OpenCSV Version 3.8 for a longer time. Now we migrated our code to Version 5.3 and have (by now :-) two issues: First issue: We have an input file like this: "A-column","B-column" 1 2 The bean is mapped to "A-column" and "B-column" by HeaderColumnNameTranslateMappingStrategy. The B-column value is optional. The effect in 5.3 is that NO line is parsed: We got an emty list - no error is thrown Changing it to ... "A-column","B-column" 1, 2, ... makes it work. But the problem is...

Hi, we have been using OpenCSV Version 3.8 for a longer time. Now we migrated our code to Version 5.3 and have (by now :-) two issues: First issue: We have an input file like this: "A-column","B-column" 1 2 The bean is mapped to "A-column" and "B-column" by HeaderColumnNameTranslateMappingStrategy. The B-column value is optional. The effect in 5.3 is that NO line is parsed: We got an emty list - no error is thrown Changing it to ... "A-column","B-column" 1, 2, ... makes it work. But the problem is...