What would be the impact of changing slf4j logging signatures to
accept object instead of string?
Scott
On Oct 4, 2009, at 11:53 AM, Jess Holle <[email protected]> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
