Decebal Suiu

In the end I solved the problem with an override of determineConverter: HeaderColumnNameTranslateMappingStrategy<HistoricalQuote> strategy = new HeaderColumnNameTranslateMappingStrategy<>() { @Override protected CsvConverter determineConverter(Field field, Class<?> elementType, String locale, String writeLocale, Class<? extends AbstractCsvConverter> customConverter) throws CsvBadConverterException { if ("date".equals(field.getName())) { ZonedDateTimeConverter converter = new ZonedDateTimeConverter(dateFormatter);...

I have the same problem (missing convertValue method). My problem is that I have a bean (POJO) and multiple CSV providers. Each provider comes with different format for a ZonedDateTime field from bean (it's only an example). My impression is that version 5 comes to improve the part with annotation but unfortunately not everything comes down to annotations. I need a method to achieve the same result programatically, without to use annotations (converter in my particular example). HeaderColumnNameTranslateMappingStrategy<HistoricalQuote>...

I have the same problem (missing convertValue method). My problem is that I have a bean (POJO) and multiple CSV providers. Each provider comes with different format for a Date field from bean (it's only an example). My impression is that version 5 comes to improve the part with annotation but unfortunately not everything comes down to annotations. I need a method to achieve the same result programatically, without to use annotations (converter in my particular example). HeaderColumnNameTranslateMappingStrategy<HistoricalQuote>...

I have the same problem (missing convertValue method). My problem is that I have a bean (POJO) and multiple CSV providers. Each provider comes with different format for a Date field from bean (it's only an example). My impression is that version 5 comes to improve the part with annotation but unfortunately not everything comes down to annotations. I need a method to achieve the same result problematically, without to use annotations (converter in my particular example). HeaderColumnNameTranslateMappingStrategy<HistoricalQuote>...

I have the same problem (missing convertValue method). My problem is that I have a bean (POJO) and multiple CVS providers. Each provider comes with different format for a Date field from bean (it's only an example). My impression is that version 5 comes to improve the part with annotation but unfortunately not everything comes down to annotations. I need a method to achieve the same result problematically, without to use annotations (converter in my particular example). HeaderColumnNameTranslateMappingStrategy<HistoricalQuote>...

I have the same problem (missing convertValue method). My problem is that I have a bean (POJO) and multiple CVS providers. Each provider comes with different format for a Date field from bean (it's only an example). My impression is that version 5 comes to improve the part with annotation but unfortunately not everything comes down to annotations. I need a method to achieve the same result problematically, without to use annotations (converter in my particular example). HeaderColumnNameTranslateMappingStrategy<HistoricalQuote>...

Do you know other libraries similar with JETT and JXLS?

Thanks Etienne for your detailed response. I tried to look for other Open Source...