Package org.apache.log4j

While pax-logging-api bundle exports org.apache.log4j package (and makes some methods no-op), pax-logging-service bundle has to Private-Package some of the classes from the same package.

See: Description

Class Summary

Class	Description
AsyncAppender	The AsyncAppender lets users log events asynchronously.
Category	This class has been deprecated and replaced by the Logger subclass.
ConsoleAppender	ConsoleAppender appends log events to System.out or System.err using a layout specified by the user.
DailyZipRollingFileAppender	DailyZipRollingFileAppender extends FileAppender so that the underlying file is rolled over at a user chosen frequency.
OsgiThrowableRenderer	Enhanced implementation of ThrowableRenderer.
PaxLoggingConfigurator	OSGi-specific PropertyConfigurator that can parse log4j.properties file and dynamically reference some log4j services (appenders, layouts, error handlers, filters) from OSGi registry.
SanitizingPatternLayout	A PatternLayout that allows you to trim and sanitize a logging event message to avoid security issues like: https://cwe.mitre.org/data/definitions/117.html

Package org.apache.log4j Description

While pax-logging-api bundle exports org.apache.log4j package (and makes some methods no-op), pax-logging-service bundle has to Private-Package some of the classes from the same package.

Normally classes from this package will be loaded using OSGi import from pax-logging-api bundle, but when needed, some classes from original log4j:log4j JAR have to be shaded here (and not exported).

This is especially important for org.apache.log4j.Logger class itself - pax-logging-api exports this class to be used as API of Log4J1, but pax-logging-service has to use own (and unchanged - except when fixing some performance/synchronization issues) copy from log4j:log4j. But also other classes from this package have to be shaded. General rule is - if pax-logging-api changes some class from Log4J1 (usually to no-op some methods), pax-logging-service should use own copy.