DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42023>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42023


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED




------- Additional Comments From [EMAIL PROTECTED]  2007-08-28 10:18 -------
To clarify the original submission, the later scenario from above is what I am
referring to.  I believe it is a design flaw for the log4j paradigm to fall
apart when LoggingEvents are serialized.  Log4j should either cause serialized
message objects to be reconstituted when a LoggingEvent is deserialized (which
is what my patch accomplishes), or should refuse to allow logging of arbitrary
message objects.

I understand the need for keeping the SocketAppender and SocketReceiver
unchanged, but the sample patch I submitted should accomplish the intended
purpose while being completely transparent to the rest of the log4j codebase,
including any Appenders.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to