You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles Sadowski (Jira)" <ji...@apache.org> on 2019/11/27 01:48:00 UTC
[jira] [Created] (GEOMETRY-65) Use of "Serializable"
Gilles Sadowski created GEOMETRY-65:
---------------------------------------
Summary: Use of "Serializable"
Key: GEOMETRY-65
URL: https://issues.apache.org/jira/browse/GEOMETRY-65
Project: Apache Commons Geometry
Issue Type: Task
Components: core, Euclidean 1D, Euclidean 2D, Euclidean 3D, Spherical 1D, Spherical 2D
Reporter: Gilles Sadowski
Many classes are declared to be {{Serializable}}. But in effect they are not because some of their fields are not {{Serializable}} (this is reported by "soundcloud.io").
In my opinion, the
{code}
implements Serializable
{code}
declaration must be removed from all classes but those explicitly designed for persistence. Actually, even for those, I'd favour a design where persistence is implemented "externally" (i.e. *not* by {{Serializable}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)