Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Log4j has been around for a long time, and it works very well. I have no scientific study to back it, but based on what I've seen at a large number of clients, it is easily the logging framework that I see used more than any other. It has been around for a long time, and not been replaced by the Next Big Logging Framework, which says something. </p> <p>It is dead simple to set up, and easy to learn the basic appenders (outputs). There are a whole host appenders that are available, including:</p> <ol> <li>ConsoleAppender</li> <li>DailyRollingFileAppender</li> <li>ExternallyRolledFileAppender </li> <li>FileAppender</li> <li>JDBCAppender</li> <li>JMSAppender</li> <li>NTEventLogAppender</li> <li>RollingFileAppender</li> <li>SMTPAppender</li> <li>SocketAppender</li> <li>SyslogAppender</li> <li>TelnetAppender</li> <li>WriterAppender</li> </ol> <p>Plus others. It isn't difficult to write your own appender either. Additionally there is a great deal of flexibility in each of the appenders that allow you to control specifically what is output in your log.</p> <p>One note, I had a series of classloader problems when I used apache commons logging in addition to log4j. It was only for one specific application, but I found it simpler to use log4j alone, rather than to have the flexibility offered when using an abstraction layer like commons logging. </p> <p>See this article for <a href="http://www.qos.ch/logging/thinkAgain.jsp" rel="noreferrer">more details</a>:</p> <p>Good luck!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload