When logback cannot find configuration file anywhere, it sets the default to
send everything to standard output and the level is set to DEBUG.
This creates a big problem in our production environment: super-verbose log
that is even difficult to look at.
My solution was to create a small wrapper using JoranConfigurator. This works
great, and I can do whatever I need.
However, here is the downside: my code is no longer ignorant of logback.
Previously it was purely slf4j everywhere, but now every class is indirectly
dependent on logback stuff (though it is limited to 2 lines in every java
file). This defeats the purpose of slf4j as pure facade.
Is there any better solution?
Our problem is, we need to guarantee that no matter what happens in the logging
layer, it should never go wild and produce all that debugging noise.
________________________________
This email, along with any attachments, is confidential and may be legally
privileged or otherwise protected from disclosure. Any unauthorized
dissemination, copying or use of the contents of this email is strictly
prohibited and may be in violation of law. If you are not the intended
recipient, any disclosure, copying, forwarding or distribution of this email is
strictly prohibited and this email and any attachments should be deleted
immediately. This email and any attachments do not constitute an offer to sell
or a solicitation of an offer to purchase any interest in any investment
vehicle sponsored by Moon Capital Management LP ("Moon Capital"). Moon Capital
does not provide legal, accounting or tax advice. Any statement regarding
legal, accounting or tax matters was not intended or written to be relied upon
by any person as advice. Moon Capital does not waive confidentiality or
privilege as a result of this email.
_______________________________________________
Logback-user mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-user
