commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NET-463) Does it make sense for NET classes to be Serializable?
Date Thu, 12 Feb 2015 20:44:13 GMT

     [ https://issues.apache.org/jira/browse/NET-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb updated NET-463:
---------------------
    Issue Type: Task  (was: Bug)

> Does it make sense for NET classes to be Serializable?
> ------------------------------------------------------
>
>                 Key: NET-463
>                 URL: https://issues.apache.org/jira/browse/NET-463
>             Project: Commons Net
>          Issue Type: Task
>            Reporter: Sebb
>
> A few of the NET classes currently implement Serializable.
> However, it's doubtful that serialization would actually work.
> There are no unit tests.
> Also, what is the use-case for it?
> Can we drop the Serializable references?
> The classes that implement Serializable currently are:
> ftp.FTPFile
> ntp.TimeStamp
> util.ListenerList (contains non-serialisable field of type CopyOnWriteArrayList)
> ProtocolCommandSupport



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message