You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/08/03 12:11:56 UTC
DO NOT REPLY [Bug 42023] LoggingEvent Message Object is lost upon
serialization
https://issues.apache.org/bugzilla/show_bug.cgi?id=42023
--- Comment #3 from Thorbjørn Ravn Andersen <th...@gmail.com> 2008-08-03 03:11:56 PST ---
I don't think that an "old" SocketAppender and a "new" SocketReciver can talk
together with your patch.
I think it would be better to create a super class of LoggingEvent which has
the serializable field, and then create a SocketAppenderIncludingLoggingEvent
(or something) appender which does the necessary voodoo as it will be backward
compatible.
Could you elaborate on the circumstances where this missing field is an issue
when deserialized?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org