|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||
See:
Description
| Class Summary | |
| Level |
This class is equivalent to java.util.logging.Level.
|
| Logger |
This class is similar to java.util.logging.Logger, that
contains a subset of method calls that are mainly for writing log
messages.
|
| LogManager |
This class is similar to java.util.logging.LogManager.
|
| PropertiesConfigurator13 |
This is based on com.sap.tc.logging.PropertiesConfigurator
but with modified code to wrap around the configuration for JSR 47 API as in
JDK 1.4. |
Provides the SUN compliant standard logging API in the JDK1.3 working environment, to support forward compatibility to JDK1.4.
The SUN standard logging API is not available until JDK1.4. If you are working with JDK1.3, and would like to start enabling logging in your code with the SUN compliant logging API, then you can use this package to work on the logging as if you are working with JDK1.4. Note that this is based on the API released in JDK1.4 beta 2.
Basic idea:
import com.sap.tc.loggingStandard; and
make sure loggingStandard.jar is included in the classpath.
Insert logging statement as if you are using the java.util.logging
API in a JDK1.4 environment.
Theoretically, when you are ready to migrate to a JDK1.4 setting, there
should be minimal change in your code, eg. switching import statment, and the
rest should stay intact.
The output will be in SAP logging format.
Configuration:
The configuration part of a logging tool is decoupled from the source code
(true in both cases for SAP and SUN). Note that configuration of this standard wrapper
uses the SAP defined configuration file to control the logging behavior.This
corresponds to the default configuration file used in SUN, "lib/logging.properties"
under the JRE directory.
There are differences between the SAP & SUN configuration syntax, especailly on
the terminology. For your convenience, the major part of the configuration has
been wrapped for you to ease out the learning curve. As a matter of fact, this
configuration version even enhances the specification ability on top of that
provided by SUN.
Please refer to PropertiesConfigurator13 for more details.
Most of the configuration parts have been mapped. The SAP logging features have been
hidden BUT one: Filters. After all, internally SAP logging objects are used.
Filter is an optional feature,
and users have to implement their own filters. In case you intend to do this, you
have to implement the filter based on the Filter,
with respect to the LogRecord. Both SUN & SAP
APIs allow you to do filtering on a log record. Though the definitions of Log Record
are different under SUN & SAP, they are very similar. It should be sufficient at this
moment to implement a filter on top of the SAP log record.
Extra note: unlike the SUN specifications, the tool is capable of taking on multiple
filters. The syntax and logic of specifying in the config. file is identical to that for
handlers.
|
|||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | ||||||||