[ http://jira.qos.ch/browse/LBCLASSIC-163?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-163: --------------------------------------- I took the easy way out. 1. I changed LoggingEventVO so that only StructuredData objects are serialized. All others are serialized to Strings as was previously done. 2. JMSTopicAppender, JMSQueueAppender and SocketAppender can be configured with a PreSerializationTransformer. This allows the serialization to be done any way desired. However, SocketNode, JMSTopicSink and JMSQueueSink still do not provide a way to override the way they deserialize objects. I propose adding a DeSerializationTransformer that can be configured in. Alternately, the deserialization method could be added to the PreSerializationTransformer - in which case the PreSerializationTransformer interface name should be renamed. 3. JMSTopicAppender, JMSQueueAppender and SocketAppender all will use the LayoutPreSerializationTransformer if a layout is configured and no PreSerilalizationTransformer is provided.
LoggingEventVO does not serialize the argument array properly. --------------------------------------------------------------
Key: LBCLASSIC-163 URL: http://jira.qos.ch/browse/LBCLASSIC-163 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.917 Reporter: Ralph Goers Assignee: Logback dev list
LoggingEventVO serializes the objects in the argument array by simply calling toString(). This makes it impossible to reconstruct the objects on the remote side. I have fixed this in my fork at git://github.com/rgoers/logback.git by serializing the object if it implements Serializable and converting it to a String if it does not.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira