[logback-dev] RFC: LoggingEvent redesign
rgoers at apache.org
Tue Feb 24 01:15:58 CET 2009
I'm -1 on this recommendation. SLF4J and Logback require messages to
be Strings. I "cheat" in audit logging by passing a Map as one of the
parameters. Although the Map can be serialized and deserialized the
cost of doing that is very high when the Map is just being passed to a
local Appender. FWIW - I'm planning on adding this Auditing
capability to XLogger in the near future.
On Feb 23, 2009, at 2:34 PM, Joern Huxhorn wrote:
> I also still think that the LoggingEvent should not know about the
> logic behind the transformation from the Object arguments to the
> String arguments.
> Therefore I'd suggest to define void setArgumentArray(String)
> instead of void setArgumentArray(Object) (see http://jira.qos.ch/browse/LBCLASSIC-45
More information about the logback-dev