[logback-dev] [Bug 100] Serialization of objectArray in LoggingEvent does not always work

[bugzilla-daemon at pixie.qos.ch]

show_bug.cgi?id=100





--- Comment #20 from Walter Smith <walter.smith at sinntr.eu>  2009-07-05 23:18:13 ---
Hi!

(In reply to comment #19)
> I am inclined to think that the use case is
> an important one, and worth tying application code to logback's
> implementation.

I thoroughly second Cekis point of view!!! This is even a use case that we
switched from log4j to logback!

log4j completely formats the message before it creates a LogEvent. We wrote an
appender to collect statistics to be sent to a monitoring system... extracting
them from the message string is not what we think to be very robust, as you may
agree. We where glad that logback postpones the formatting until it has to.

While our specific use case is not using a remote appender, the use case is
IMHO very important! Locale specific formatting of dates and numbers is just
one convincing example.

If an Object is not Serializable, then toString would be a good option, but for
all other cases the class should get over the wire as well... but there are in
deed some very interesting issues with the same objects of the same type coming
from different machines with different versions... or one machine doing a hot
redeploy of a class!

Kind regards
Walter


-- 
Configure bugmail: userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.