My guess is that what should be done is that LoggingEvent should overide the serialization methods (writeObject & readObject) to use introspection to see of the message field's class implements the Serializable method. If so it gets written, if not it doesn't. This should only be a 30minute job at worst I think. Any thoughts?
 
sam
----- Original Message -----
Sent: Thursday, July 26, 2001 2:38 AM
Subject: RE: Design: How to do the following with Log4j

Yes, I have...if you look at the LoggingEvent.java source, you will see the problem is that the message field that Object is stored is is marked "transient" which means it WILL NOT be serialized and sent across the wire. It looks like only the String representation was meant to be shipped to a remote server and NOT the whole object.
 
Any reasons why this can't be changed?
 
- Tim

Reply via email to