java.lang.Object | |
↳ | sun.rmi.runtime.Log |
Utility which provides an abstract "logger" like RMI internal API which can be directed to use one of two types of logging infrastructure: the java.util.logging API or the java.rmi.server.LogStream API. The default behavior is to use the java.util.logging API. The LogStream API may be used instead by setting the system property sun.rmi.log.useOld to true. For backwards compatibility, supports the RMI system logging properties which pre-1.4 comprised the only way to configure RMI logging. If the java.util.logging API is used and RMI system log properties are set, the system properties override initial RMI logger values as appropriate. If the java.util.logging API is turned off, pre-1.4 logging behavior is used.
Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
BRIEF | Logger re-definition of old RMI log values | ||||||||||
VERBOSE |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Access logs associated with boolean properties
Do not call getLog multiple times on the same logger name.
| |||||||||||
Access log for a tri-state system property.
| |||||||||||
"logger like" API to be used by RMI implementation
| |||||||||||
get and set the RMI server call output stream
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() |
Access logs associated with boolean properties Do not call getLog multiple times on the same logger name. Since this is an internal API, no checks are made to ensure that multiple logs do not exist for the same logger.
Access log for a tri-state system property. Need to first convert override value to a log level, taking care to interpret a range of values between BRIEF, VERBOSE and SILENT. An override < 0 is interpreted to mean that the logging configuration should not be overridden. The level passed to the factories createLog method will be null in this case. Note that if oldLogName is null and old logging is on, the returned LogStreamLog will ignore the override parameter - the log will never log messages. This permits new logs that only write to Loggers to do nothing when old logging is active. Do not call getLog multiple times on the same logger name. Since this is an internal API, no checks are made to ensure that multiple logs do not exist for the same logger.
get and set the RMI server call output stream