You would still be able to pass arbitrary objects but with a different syntax.
logger.info("{}", someObject);
instead of the current
logger.info(someObject);
Jess Holle wrote:
Code using using org.apache.log4j.Logger would continue to work as is,
ensuring backward compatibility, at least as far as the log4j
signatures are concerned. Users who rely on the fact that the message
argument was an Object instead of String would need to modify few
lines of code. In the worst case, this change could cause loss of
logging information but would NOT cause compile-time problems or
issues related to method signatures.
This is a key ability in log4j, which I for one leverage to pass
complex, structured data to specialized loggers, e.g. to dissect these
structures and place various fields into separate relational database
columns.
Losing first class access to such abilities is a non-starter.
--
Jess Holle
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
