dido:public:ra:xapend:xapend.b_stds:defact:apache:log4j
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:apache:log4j [2020/05/16 16:00] char |
dido:public:ra:xapend:xapend.b_stds:defact:apache:log4j [2021/11/08 17:02] (current) nick ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Apache: Log4j ===== | ===== Apache: Log4j ===== | ||
| - | [[dido:public:ra:xapend.stds:defact:apache| return to the Apache Foundation ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:apache:start| return to the Apache Foundation ]] |
| - | : **Note**: The following is an excerpt from the official Apache Log4j site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the official Apache Log4j site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
| : // | : // | ||
| Line 22: | Line 22: | ||
| Source: [[https://logging.apache.org/log4j/2.x/log4j-users-guide.pdf | Log4J User's Guide ]] | Source: [[https://logging.apache.org/log4j/2.x/log4j-users-guide.pdf | Log4J User's Guide ]] | ||
| ==== Introduction ==== | ==== Introduction ==== | ||
| - | : //Almost every large application includes its own logging or tracing API. In conformance with this | + | : //Almost every large [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] includes its own logging or tracing [[dido:public:ra:xapend:xapend.a_glossary:a:api|API]]. In conformance with this |
| rule, the E.U. SEMPER project decided to write its own tracing API. This was in early 1996. After | rule, the E.U. SEMPER project decided to write its own tracing API. This was in early 1996. After | ||
| countless enhancements, several incarnations and much work that API has evolved to become log4j, | countless enhancements, several incarnations and much work that API has evolved to become log4j, | ||
| a popular logging package for Java. The package is distributed under the Apache Software License, | a popular logging package for Java. The package is distributed under the Apache Software License, | ||
| a fully-fledged open source license certified by the open source initiative. The latest log4j version, | a fully-fledged open source license certified by the open source initiative. The latest log4j version, | ||
| - | including full-source code, class files and documentation can be found at http://logging.apache.org/ | + | including full-[[dido:public:ra:xapend:xapend.a_glossary:s:sourcecode|source code]], [[dido:public:ra:xapend:xapend.a_glossary:c:class|class]] files and documentation can be found at http://logging.apache.org/ |
| log4j/2.x/index.html.// | log4j/2.x/index.html.// | ||
| : //Inserting log statements into code is a low-tech method for debugging it. It may also be the only way | : //Inserting log statements into code is a low-tech method for debugging it. It may also be the only way | ||
| because debuggers are not always available or applicable. This is usually the case for multithreaded | because debuggers are not always available or applicable. This is usually the case for multithreaded | ||
| - | applications and distributed applications at large.// | + | applications and [[dido:public:ra:xapend:xapend.a_glossary:d:dapp|distributed applications]] at large.// |
| : //Experience indicates that logging was an important component of the development cycle. It offers several advantages. It provides precise context about a run of the application. Once inserted into the code, the generation of logging output requires no human intervention. Moreover, log output can be saved in persistent medium to be studied at a later time. In addition to its use in the development cycle, a sufficiently rich logging package can also be viewed as an auditing tool.// | : //Experience indicates that logging was an important component of the development cycle. It offers several advantages. It provides precise context about a run of the application. Once inserted into the code, the generation of logging output requires no human intervention. Moreover, log output can be saved in persistent medium to be studied at a later time. In addition to its use in the development cycle, a sufficiently rich logging package can also be viewed as an auditing tool.// | ||
| Line 40: | Line 40: | ||
| : //"As personal choice, we tend not to use debuggers beyond getting a stack trace or the value of a variable or two. One reason is that it is easy to get lost in details of complicated data structures and control flow; we find stepping through a program less productive than thinking harder and adding output statements and self-checking code at critical places. Clicking over statements takes longer than scanning the output of judiciously-placed displays. It takes less time to decide where to put print statements than to single-step to the critical section of code, even assuming we know where that is."// | : //"As personal choice, we tend not to use debuggers beyond getting a stack trace or the value of a variable or two. One reason is that it is easy to get lost in details of complicated data structures and control flow; we find stepping through a program less productive than thinking harder and adding output statements and self-checking code at critical places. Clicking over statements takes longer than scanning the output of judiciously-placed displays. It takes less time to decide where to put print statements than to single-step to the critical section of code, even assuming we know where that is."// | ||
| - | : //More important, debugging statements stay with the program; debugging sessions are transient. Logging does have its drawbacks. It can slow down an application. If too verbose, it can cause scrolling blindness. To alleviate these concerns, log4j is designed to be reliable, fast and extensible. Since logging is rarely the main focus of an application, the log4j API strives to be simple to understand and to use.// | + | : //More important, debugging statements stay with the program; debugging sessions are transient. Logging does have its drawbacks. It can slow down an application. If too verbose, it can cause scrolling blindness. To alleviate these concerns, log4j is designed to be reliable, fast and extensible. Since logging is rarely the main focus of an application, the log4j [[dido:public:ra:xapend:xapend.a_glossary:a:api|API]] strives to be simple to understand and to use.// |
| | | ||
| ==== Features ==== | ==== Features ==== | ||
| Line 56: | Line 56: | ||
| * Creates a PHP user-level message using the PHP trigger_error() function. | * Creates a PHP user-level message using the PHP trigger_error() function. | ||
| * A network socket. | * A network socket. | ||
| - | * [[dido:public:ra:xapend.stds:tech:ietf:syslog| Syslog]] | + | * [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:syslog| Syslog]] |
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/defact/apache/log4j.1589659201.txt.gz · Last modified: 2020/05/16 16:00 by char
