Recent changes to bugs

onStart() not called when using CSVParser2

Luc — Tue, 10 Nov 2009 17:38:20 -0000

When setting a listener, the onStart() method is not called when parsing a file.

CSVParser2 disregard continueParsingIfErrors

Luc — Tue, 10 Nov 2009 17:22:21 -0000

CSVParser2 will throw exceptions even if continueParsingIfErrors property is set to true.

CSVBeans does not adhere to RFC4180

Prasad Kulkarni — Thu, 02 Apr 2009 10:58:35 -0000

I have a csv file where some fields might contain comma.
a,b,c,"c,d",e

There is no way to parse the above record correctly.
Kindly suggest.

Or else this is a bug,
The following RFC(http://www.ietf.org/rfc/rfc4180.txt) clearly mentions at point 2.5, that

Fields containing line breaks (CRLF), double quotes, and commas
should be enclosed in double-quotes. For example:

"aaa","b CRLF
bb","ccc" CRLF
zzz,yyy,xxx

Kindly fix this urgently, or let us know a resolution.

Date Converter does not handle null dates

Anonymous — Thu, 15 May 2008 14:50:04 -0000

The code in the data converter checks the class type before checking to see if the class is null. In most cases a blank date will yield a null and the date converter will die in converting that object. If the date converter can check for null first and then return blank string or something configurable instead of dying that would be preferred.

New Line character within data

Anonymous — Wed, 06 Feb 2008 03:32:05 -0000

Csv parsing fails if there is a new line character within data even though the data is encapsulated within quotes (its a valid csv, open fine in excel).

character problem

Anonymous — Thu, 27 Jul 2006 12:34:26 -0000

here is the mapping filter...

successful parsing depends upon the name of bean. I
know it sounds strange. but it is the fact. some names
like dstable works, PdsTable fails to initialise the
object.