OpenCSV Java - CsvToBeanFilter using annotated objects instead of a HeaderColumnNameTranslateMappingStrategy
up vote
0
down vote
favorite
I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy
to associate columns in my Object to those in the input data and it all works fine.
In addition, I've implemented a CsvToBeanFilter
to filter out data before the objects are constructed to improve performance.
What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy
and move to annotated fields on my object.
The provided example for CsvToBeanFilter
however, seem to be referring to the MappingStrategy
to get the column outside of the object.
Any ideas how I can do this with annotated fields?
From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.
java opencsv
add a comment |
up vote
0
down vote
favorite
I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy
to associate columns in my Object to those in the input data and it all works fine.
In addition, I've implemented a CsvToBeanFilter
to filter out data before the objects are constructed to improve performance.
What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy
and move to annotated fields on my object.
The provided example for CsvToBeanFilter
however, seem to be referring to the MappingStrategy
to get the column outside of the object.
Any ideas how I can do this with annotated fields?
From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.
java opencsv
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy
to associate columns in my Object to those in the input data and it all works fine.
In addition, I've implemented a CsvToBeanFilter
to filter out data before the objects are constructed to improve performance.
What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy
and move to annotated fields on my object.
The provided example for CsvToBeanFilter
however, seem to be referring to the MappingStrategy
to get the column outside of the object.
Any ideas how I can do this with annotated fields?
From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.
java opencsv
I'm reading a CSV file and am using a HeaderColumnNameTranslateMappingStrategy
to associate columns in my Object to those in the input data and it all works fine.
In addition, I've implemented a CsvToBeanFilter
to filter out data before the objects are constructed to improve performance.
What I would like to do is move away from HeaderColumnNameTranslateMappingStrategy
and move to annotated fields on my object.
The provided example for CsvToBeanFilter
however, seem to be referring to the MappingStrategy
to get the column outside of the object.
Any ideas how I can do this with annotated fields?
From the fact the supplied documentation doesn't compile, and references a deprecated method makes me think I might be out of luck.
java opencsv
java opencsv
asked Nov 10 at 19:14
Jakg
19710
19710
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Cross-posting from the bug report I filed.
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.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Cross-posting from the bug report I filed.
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.
add a comment |
up vote
0
down vote
accepted
Cross-posting from the bug report I filed.
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.
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Cross-posting from the bug report I filed.
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.
Cross-posting from the bug report I filed.
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.
answered Nov 10 at 20:13
Jakg
19710
19710
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242524%2fopencsv-java-csvtobeanfilter-using-annotated-objects-instead-of-a-headercolumn%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown