Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Corona Logging"
(→OSGi Log Service) |
|||
| Line 1: | Line 1: | ||
== OSGi Log Service == | == OSGi Log Service == | ||
| + | |||
| + | Corona Logging uses OSGi Log Service. OSGi specifies two log services: | ||
| + | * Log Service - allows bundles to log information including a message, a level, an exception, a ServiceReference object, and a Bundle object | ||
| + | * Log Reader Service - allows bundles to access a list of LogEntry objects, and allows the registration of a LogListener object that receives LogEntry objects as they are created. | ||
| + | |||
| + | To extend control over log statements [http://logging.apache.org/log4j/docs/ log4j package] is used. It is plugged into Corona through LogListener object registered with the use of the OSGi Log Reader Service. | ||
Revision as of 06:33, 17 August 2006
OSGi Log Service
Corona Logging uses OSGi Log Service. OSGi specifies two log services:
- Log Service - allows bundles to log information including a message, a level, an exception, a ServiceReference object, and a Bundle object
- Log Reader Service - allows bundles to access a list of LogEntry objects, and allows the registration of a LogListener object that receives LogEntry objects as they are created.
To extend control over log statements log4j package is used. It is plugged into Corona through LogListener object registered with the use of the OSGi Log Reader Service.