https://issues.apache.org/bugzilla/show_bug.cgi?id=42023
Curt Arnold <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |WONTFIX
--- Comment #4 from Curt Arnold <[EMAIL PROTECTED]> 2008-08-05 22:28:05 PST ---
Discarding the message object and only transmitting the rendered form was an
explicit and documented design decision in log4j 1.2. It is much too late to
surprise existing users who may be using an expensive to serialize message
object with a potentially huge performance hit on a maintenance release.
Changing the API to not allow arbitrary objects is even worse than a
performance hit. We absolutely can't change the API in anything other than a
major release.
I have added a log4j 2.0 bug to keep this on the log4j 2.0 radar
(https://issues.apache.org/jira/browse/LOG4J2-21).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
