[
https://issues.apache.org/jira/browse/LOG4J2-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478087#comment-17478087
]
Ralph Goers edited comment on LOG4J2-3228 at 1/18/22, 5:59 PM:
---------------------------------------------------------------
We should remove Serializable from anywhere it won't break compatibility. I
can't imagine why anyone would be expecting that interface unless they are
performing serialization, which we want to prevent.
For example, if a user has implement a custom Message that extends
Serializable. The fact that we no longer extend Serializable shouldn't cause a
problem so long as there is no code expecting it.
was (Author: [email protected]):
We should remove Serializable from anywhere it won't break compatibility. I
can't imagine why anyone would be expecting that interface unless they are
performing serialization, which we want to prevent.
> Nothing should implement Serializable in Log4j 3
> ------------------------------------------------
>
> Key: LOG4J2-3228
> URL: https://issues.apache.org/jira/browse/LOG4J2-3228
> Project: Log4j 2
> Issue Type: Story
> Reporter: Gary D. Gregory
> Priority: Major
> Fix For: 3.0.0
>
>
> Like Effective Java #85.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
