The logging support in the standard Log Service of the OSGi specification is minimalistic and not entirely suitable for enterprise applications. This project tries to address this by extending the standard interface with additional interfaces and using a strong logging backend, the Apache Log4J. Pax Logging defines its own API, but more importantly it supports the Log4J and Jakarta Commons Logging APIs as well, making it easy to create bundles that use these common APIs, either directly in new code or indirectly from inside 3rd party libraries.
Features
- Log4J driving the backend implementation.
- Log4J API supported.
- Jakarta Commons Logging API supported.
- Pax Logging Service implements the standard OSGi Log Service API.
- JDK Logging API support.
- Avalon Logger API support.
- SLF4J API support.
- Knopflerfish Log service support.
- Tomcat Juli API support.
Latest News
Pax Logging 1.11.6 and 2.0.3 were released with Log4j2 upgrade to version 2.13.2 due to CVE-2020-9488: https://issues.apache.org/jira/browse/LOG4J2-2819
These releases do not contain any other changes.
Pax Logging 1.10.6 has been released where thanks to Monica Ron all discovered memory issues where solved (as proved by integration tests backported from 1.11.x) - thanks again!
Checkout the release notes Pax Logging 1.10.6 for more details.
Pax Logging 2.0.2 has been released with one improvement. It can now be used without Configuration Admin while preserving all configuration methods.
Configuration page shows how to use Pax Logging without Configuration Admin and how to use org.ops4j.pax.logging.property.file system or bundle context property to specify actual Configuration file (for any of the backends).
Here’s a list of fixed JIRA issues: