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=31662>. 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=31662 message property in LoggingEvent class not serializable [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2004-10-12 21:22 ------- I still think it should be serializable, giving the fact that most people use getRenderedMessage() instead to retrive text message. For a special group people, the message field can be very useful. E.g in my case, instead of conventionally log a log4j message, I am tring to leverage log4j interface to generate very useful application report data into database schemas, which later on any management staff can generate application reports using a report tool like crystal reports. In order to do that, a text message that lum sum all reporting information is not good enough, it should be structured, i.g. be object, so that the object can tell what data in it and which database table it should go into. This, if enabled, open an new applcation field of log4j -- reporting. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
