Jukka Zitting wrote:
Anyway, what I was trying to say is that you can typically get away with less detailed log messages when you have access to the source code (and understand it, e.g. you known how the controller in your example it works) and detailed logging metadata (thread names, line numbers, stack trackes, etc.). But in cases where this is not true (and given the purpose of SLF4J, I'd argue that this applies to the majority of SLF4J deployments), a clear log message is often extremely useful.
Hi Jukka, Are you saying in the majority of SLF4J deployments the thread name is not available? By implication, I deduce that in your opinion the majority of deployments use j.u.l. as the underlying logging framework. Is that correct?
BR, Jukka Zitting
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev
