[
https://issues.apache.org/jira/browse/CSV-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Herbert closed CSV-248.
----------------------------
Resolution: Fixed
Serialization functionality is restored.
A test was added to assert the record after deserialisation in commit
8d6772a3209b124af7e2430f69cdf6a7c765fd44.
A test was added to deserialise a record that was serialised using version 1.6
in commit 66c34da258f068046536d84e712a90a5f7f6e2a0.
> CSVRecord is not Serializable
> -----------------------------
>
> Key: CSV-248
> URL: https://issues.apache.org/jira/browse/CSV-248
> Project: Commons CSV
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Alex Herbert
> Priority: Major
> Fix For: 1.8
>
>
> CSVRecord is no longer Serializable as it stores the CSVParser and that is
> not serializable.
> The parser contains a list of all the CSVRecords. So to serialize this would
> serialize a lot of extra information. The cascade of serialization eventually
> includes the original BufferedReader used to read the data.
> The parser is required for the header map functionality and the getParser()
> method. The easy fix is to not support any functionality related to the
> parser after deserialization. If the header map functionality is to be
> supported the class can store the header map (easy), or overload the
> serialization methods to record and load the header map (more effort), or
> something else.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
