Public Member Functions | |
JacORBLoggerFactory () | |
final String | getLoggingBackendName () |
org.apache.avalon.framework.logger.Logger | getNamedLogger (String name) |
org.apache.avalon.framework.logger.Logger | getNamedLogger (String name, String fileName, long maxFileSize) throws IOException |
org.apache.avalon.framework.logger.Logger | getNamedRootLogger (String name) |
void | setDefaultLogFile (String fileName, long maxLogSize) throws IOException |
void | configure (Configuration conf) throws ConfigurationException |
Private Attributes | |
Jdk14Logger | delegate |
int | jacOrbVerbosity |
Static Private Attributes | |
final String | BACKEND_NAME = "jdk14" |
jacorb.log.loggerFactory
property. It creates Loggers through alma.acs.logging.ClientLogManager, which ensures that JacORB logs will be inserted in the central ACS log stream.
These loggers will be configured through the normal ACS logging configuration mechanisms, whereas the properties jacorb.log.default.verbosity
, jacorb.logfile.append
, and jacorb.log.default.log_pattern
will be ignored. Note that at the moment we do use jacorb.log.default.verbosity
as a workaround!
|
|
|
|
|
|
|
Same as getNamedLogger(String). The file is ignored, and a respective warning message gets logged.
|
|
Returns an avalon logger which wraps the JDK logger obtained from ClientLogManager.
|
|
Returns getNamedLogger(String). The distinction between root loggers and other loggers we don't need here, since the questions of console vs. file vs. remote logging are left to ACS.
|
|
We ignore the log file, since ACS loggers forward to the central Log service.
|
|
|
|
|
|
verbosity level 0-4 from jacorb property |