CsvToBeanFilter Documentation
Brought to you by:
aruckerjones,
sconway
Menu
▾
▴
#185 CsvToBeanFilter Documentation
The example code in the documentation of the CsvToBeanFilter class doesn't compile.
The first thing is the class' constructor has the wrong name.
However, when you fix this it's then depending on a deprecated method (com.opencsv.bean.MappingStrategy.getColumnIndex(String)) which ironically has the deprecation message of "There is no replacement for this method, since we are not aware of a use for it. Let us know if you have a use case."
I am getting started with CsvToBeanFilters and would appreciate any pointers if I'm looking in the wrong place.
Yeah, you've caught us at an inopertune moment. I became aware of that use for getColumnIndex() after I deprecated it, and the replacement for CsvToBeanFilter (BeanVerifier) is in master, but hasn't been released yet. Right now, just use the deprecated getColumnIndex() if you have to. It should be very easy to move from CsvToBeanFilter to BeanVerifier once 4.4 is released.
I'll take care of the documentation error another time, but thanks very much for pointing it out. I believe in flawless documentation.
Thanks for getting back to me.
Any ideas when 4.4 is likely to be released? I think that that would have some interesting applications for me.
Fixed the error in the constructor name in the documentation.
I don't know right now when 4.4 will be released. I'm consulting with the head developer.
Andrew, Jack - sorry it took so long to get back to you. Looking at the feature and bug requests I see nothing worth holding up a release so I will look at doing a 4.4 release this weekend.
Scott :)
4.4 is released. Please fell free to test it.
thanks, i will have a look at this. Would i be right in assuming that the BeanVerifier is slower than CsvToBeanFilter?
Only in that the input is fully converted into a bean before running the verifier. That doesn't take but an instant, and it allows you to worry only about consistency of values instead of locating and converting values in an array of strings just so you can verify that the values are okay and pass them on to our code that then locates and converts them from the same array of strings.
fixed in version 4.4