commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NET-463) Does it make sense for NET classes to be Serializable?
Date Sat, 05 May 2012 17:11:51 GMT

    [ https://issues.apache.org/jira/browse/NET-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269012#comment-13269012
] 

Sebb commented on NET-463:
--------------------------

Actually CopyOnWriteArrayList is Serializable, but the entries are of type EventListener,
which may not be.
                
> 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: Bug
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message