dido:public:ra:xapend:xapend.b_stds:defact:orcle:java_logger_api
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:orcle:java_logger_api [2021/07/01 14:00] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:orcle:java_logger_api [2021/11/09 15:40] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Oracle: Java logger API ===== | ===== Oracle: Java logger API ===== | ||
| - | [[dido:public:ra:xapend:xapend.b_stds:defact:orcle| return to Oracle de facto Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:orcle:start| return to Oracle de facto Standards ]] |
| : **Note**: The following is an excerpt from the official TTTTT 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 TTTTT site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. | ||
| <table> | <table> | ||
| - | <caption>Data sheet for Java logger API</caption> | + | <caption>Data sheet for Java logger [[dido:public:ra:xapend:xapend.a_glossary:a:api|API]]</caption> |
| | Title | Java logger API (Java Platform SE-8) | | | Title | Java logger API (Java Platform SE-8) | | ||
| | Acronym | Logger | | | Acronym | Logger | | ||
| Line 17: | Line 17: | ||
| ==== Overview ==== | ==== Overview ==== | ||
| - | //Provides the classes and interfaces of the Java™ 2 platform's core logging facilities. The central goal of the logging APIs is to support maintaining and servicing software at customer sites. | + | //Provides the classes and interfaces of the Java™ 2 platform's core logging facilities. The central [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] of the logging [[dido:public:ra:xapend:xapend.a_glossary:a:api|APIs]] is to support maintaining and servicing software at customer sites. |
| There are four main target uses of the logs:// | There are four main target uses of the logs:// | ||
| Line 23: | Line 23: | ||
| - //Problem diagnosis by field service engineers. The logging information used by field service engineers may be considerably more complex and verbose than that required by system administrators. Typically such information will require extra logging within particular subsystems.// | - //Problem diagnosis by field service engineers. The logging information used by field service engineers may be considerably more complex and verbose than that required by system administrators. Typically such information will require extra logging within particular subsystems.// | ||
| - //Problem diagnosis by the development organization. When a problem occurs in the field, it may be necessary to return the captured logging information to the original development team for diagnosis. This logging information may be extremely detailed and fairly inscrutable. Such information might include detailed tracing on the internal execution of particular subsystems.// | - //Problem diagnosis by the development organization. When a problem occurs in the field, it may be necessary to return the captured logging information to the original development team for diagnosis. This logging information may be extremely detailed and fairly inscrutable. Such information might include detailed tracing on the internal execution of particular subsystems.// | ||
| - | - //Problem diagnosis by developers. The Logging APIs may also be used to help debug an application under development. This may include logging information generated by the target application as well as logging information generated by lower-level libraries. Note however that while this use is perfectly reasonable, the logging APIs are not intended to replace the normal debugging and profiling tools that may already exist in the development environment.// | + | - //Problem diagnosis by developers. The Logging APIs may also be used to help debug an [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] under development. This may include logging information generated by the target application as well as logging information generated by lower-level libraries. Note however that while this use is perfectly reasonable, the logging APIs are not intended to replace the normal debugging and profiling tools that may already exist in the development environment.// |
| //The key elements of this package include:// | //The key elements of this package include:// | ||
| - | * //**Logger** The main entity on which applications make logging calls. A Logger object is used to log messages for a specific system or application component.// | + | * //**Logger** The main [[dido:public:ra:xapend:xapend.a_glossary:e:entity|entity]] on which applications make logging calls. A Logger object is used to log messages for a specific system or application component.// |
| * //**LogRecord** Used to pass logging requests between the logging framework and individual log handlers.// | * //**LogRecord** Used to pass logging requests between the logging framework and individual log handlers.// | ||
| - | * //**Handler** Exports LogRecord objects to a variety of destinations including memory, output streams, consoles, files, and sockets. A variety of Handler subclasses exist for this purpose. Additional Handlers may be developed by third parties and delivered on top of the core platform.// | + | * //**Handler** Exports LogRecord objects to a variety of destinations including memory, output streams, consoles, files, and sockets. A variety of Handler subclasses exist for this purpose. Additional Handlers may be developed by third parties and delivered on top of the core [[dido:public:ra:xapend:xapend.a_glossary:p:platform|platform]].// |
| * //**Level** Defines a set of standard logging levels that can be used to control logging output. Programs can be configured to output logging for some levels while ignoring output for others. | * //**Level** Defines a set of standard logging levels that can be used to control logging output. Programs can be configured to output logging for some levels while ignoring output for others. | ||
| Filter: Provides fine-grained control over what gets logged, beyond the control provided by log levels. The logging APIs support a general-purpose filter mechanism that allows application code to attach arbitrary filters to control logging output.// | Filter: Provides fine-grained control over what gets logged, beyond the control provided by log levels. The logging APIs support a general-purpose filter mechanism that allows application code to attach arbitrary filters to control logging output.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/orcle/java_logger_api.1625162411.txt.gz · Last modified: 2021/07/01 14:00 by murphy
