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 [2021/07/29 11:57] murphy |
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:xapend.b_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 27: | Line 27: | ||
| 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, [[dido:public:ra:xapend:xapend.a_glossary:c:class|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.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/apache/log4j.1627574228.txt.gz · Last modified: 2021/07/29 11:57 by murphy
