Package org.ops4j.pax.logging.internal
Class JdkHandler
- java.lang.Object
-
- java.util.logging.Handler
-
- org.ops4j.pax.logging.internal.JdkHandler
-
public class JdkHandler extends Handler
JULHandlerthat bridgeslog recordsto Pax Logging loggers. Even ifSimpleFormatteris used, we only call itsFormatter.formatMessage(LogRecord)which only usesMessageFormat.format(String, Object...)method on log record's message. It doesn't do anything with remaining fields ofLogRecord.Since the backport of TLSv1.3 in java (JDK-8248721) the logic of TLS debug traces has been changed. The new TLS debug logger uses a configured JUL logger when you define the system property "javax.net.debug" as empty. The TLS log records contain additional string parameters. They are without format parameters in the log message. The
JdkHandlerappends them to the end of the TLS log message.The
JdkHandlerhas the following logging modes for the TLS log records:- no_logging - TLS messages are not logged
- no_hex_dumps_logging - all messages except hex dumps are logged
- debug_logging - all messages are logged
-
-
Constructor Summary
Constructors Constructor Description JdkHandler(PaxLoggingManager loggingManager)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description voidclose()voidflush()FormattergetFormatter()voidpublish(LogRecord record)voidsetBundleContext(org.osgi.framework.BundleContext bundleContext)-
Methods inherited from class java.util.logging.Handler
getEncoding, getErrorManager, getFilter, getLevel, isLoggable, reportError, setEncoding, setErrorManager, setFilter, setFormatter, setLevel
-
-
-
-
Constructor Detail
-
JdkHandler
public JdkHandler(PaxLoggingManager loggingManager)
-
-
Method Detail
-
setBundleContext
public void setBundleContext(org.osgi.framework.BundleContext bundleContext)
-
close
public void close() throws SecurityException- Specified by:
closein classHandler- Throws:
SecurityException
-
getFormatter
public Formatter getFormatter()
- Overrides:
getFormatterin classHandler
-
-