[ http://jira.qos.ch/browse/LBCLASSIC-163?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-163: --------------------------------------- I think you missed my point though. Why isn't a Layout sufficient to do the serialization? A Layout's purpose is to simply format the event into something useful for the purpose of the particular Appender. In the JMS case, this is just the message to be sent to the remote side where it can be processed. In some cases this might be an already formatted message and in others it might be desired to have a serialized form of the logging event. But a Layout should be able to handle either case.
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