|
SAP NetWeaver 7.20 (SP01) Composition Environment | |||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||
| Packages that use MsgObject | |
|---|---|
| com.sap.tc.logging | Provides the classes for emitting and controlling the output of trace and log messages, and the classes for organizing hierarchies of message kinds, origins and destinations. |
| Uses of MsgObject in com.sap.tc.logging |
|---|
| Methods in com.sap.tc.logging with parameters of type MsgObject | |
|---|---|
LogRecord |
Location.debug(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.debug(MsgObject msgObject)
Same as Location.log(int,
com.sap.tc.logging.MsgObject)
but always emits a debug message, that is a message of severity
Severity.DEBUG. |
LogRecord |
Location.debug(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a debug message, that is a message of severity
Severity.DEBUG. |
LogRecord |
Location.debug(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits a debug message, that is a message of severity
Severity.DEBUG. |
LogRecord |
Location.debug(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a debug message, that is a message of severity
Severity.DEBUG. |
LogRecord |
Location.error(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.error(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Category.error(Location loc,
MsgObject msgObject)
Same as Category.log(int,
Location,
MsgObject)
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Category.error(Location loc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
MsgObject,
java.lang.Object[])
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Category.error(Location loc,
String subLoc,
MsgObject msgObject)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject)
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Category.error(Location loc,
String subLoc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject,
java.lang.Object[])
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Location.error(MsgObject msgObject)
Same as #logT(int,
com.sap.tc.logging.MsgObject)
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Location.error(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Location.error(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Location.error(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits an error message, that is a message of severity
Severity.ERROR. |
LogRecord |
Location.fatal(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.fatal(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Category.fatal(Location loc,
MsgObject msgObject)
Same as Category.log(int,
Location,
MsgObject)
but always emits an fatal message, that is a message of severity
Severity.FATAL. |
LogRecord |
Category.fatal(Location loc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
MsgObject,
java.lang.Object[])
but always emits an fatal message, that is a message of severity
Severity.FATAL. |
LogRecord |
Category.fatal(Location loc,
String subLoc,
MsgObject msgObject)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject)
but always emits an fatal message, that is a message of severity
Severity.FATAL. |
LogRecord |
Category.fatal(Location loc,
String subLoc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject,
java.lang.Object[])
but always emits an fatal message, that is a message of severity
Severity.FATAL. |
LogRecord |
Location.fatal(MsgObject msgObject)
Same as Location.log(int,
com.sap.tc.logging.MsgObject)
but always emits a fatal error message, that is a message of severity
Severity.FATAL. |
LogRecord |
Location.fatal(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a fatal error message, that is a message of severity
Severity.FATAL. |
LogRecord |
Location.fatal(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits a fatal error message, that is a message of severity
Severity.FATAL. |
LogRecord |
Location.fatal(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a fatal error message, that is a message of severity
Severity.FATAL. |
LogRecord |
Location.info(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.info(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Category.info(Location loc,
MsgObject msgObject)
Same as Category.log(int,
Location,
MsgObject)
but always emits an info message, that is a message of severity
Severity.INFO. |
LogRecord |
Category.info(Location loc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
MsgObject,
java.lang.Object[])
but always emits an info message, that is a message of severity
Severity.INFO. |
LogRecord |
Category.info(Location loc,
String subLoc,
MsgObject msgObject)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject)
but always emits an info message, that is a message of severity
Severity.INFO. |
LogRecord |
Category.info(Location loc,
String subLoc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject,
java.lang.Object[])
but always emits an info message, that is a message of severity
Severity.INFO. |
LogRecord |
Location.info(MsgObject msgObject)
Same as Location.log(int,
com.sap.tc.logging.MsgObject)
but always emits an informational message, that is a message of severity
Severity.INFO. |
LogRecord |
Location.info(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits an informational message, that is a message of severity
Severity.INFO. |
LogRecord |
Location.info(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits an informational message, that is a message of severity
Severity.INFO. |
LogRecord |
Location.info(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits an informational message, that is a message of severity
Severity.INFO. |
LogRecord |
Location.log(int severity,
Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.log(int severity,
Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Category.log(int severity,
Location loc,
MsgObject msgObject)
Logs message, specified as a message object, from the given location into this category. |
LogRecord |
Category.log(int severity,
Location loc,
MsgObject msgObject,
Object[] args)
Logs message, specified as a message object, from the given location into this category. |
LogRecord |
Category.log(int severity,
Location loc,
String subLoc,
MsgObject msgObject)
Logs message, specified as a message object, from the given location into this category. |
LogRecord |
Category.log(int severity,
Location loc,
String subLoc,
MsgObject msgObject,
Object[] args)
Logs message, specified as a message object, from the given location into this category. |
LogRecord |
Location.log(int severity,
MsgObject msgObject)
Logs simple message from this location. |
LogRecord |
Location.log(int severity,
MsgObject msgObject,
Object[] args)
Logs message with parameters from this location. |
LogRecord |
Location.log(int severity,
String subloc,
MsgObject msgObject)
Same as Location.logT(int,
java.lang.String)
but appends a string denoting a sublocation to the name of this location. |
LogRecord |
Location.log(int severity,
String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.logT(int,
java.lang.String,
java.lang.Object[])
but appends a string denoting a sublocation to the name of this location. |
LogRecord |
Category.logThrowable(int severity,
Location loc,
MsgObject msgObject,
Object[] args,
Throwable exc)
Logs message with stack trace of given exception, from the given location into this category. |
LogRecord |
Category.logThrowable(int severity,
Location loc,
MsgObject msgObject,
Throwable exc)
Logs message with stack trace of given exception, from the given location into this category. |
LogRecord |
Category.logThrowable(int severity,
Location loc,
String subLoc,
MsgObject msgObject,
Object[] args,
Throwable exc)
Logs message with stack trace of given exception, from the given location into this category. |
LogRecord |
Category.logThrowable(int severity,
Location loc,
String subLoc,
MsgObject msgObject,
Throwable exc)
Logs message with stack trace of given exception, from the given location into this category. |
LogRecord |
Location.path(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.path(MsgObject msgObject)
Same as Location.log(int,
com.sap.tc.logging.MsgObject)
but always emits a path message, that is a message of severity
Severity.PATH. |
LogRecord |
Location.path(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a path message, that is a message of severity
Severity.PATH. |
LogRecord |
Location.path(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits a path message, that is a message of severity
Severity.PATH. |
LogRecord |
Location.path(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a path message, that is a message of severity
Severity.PATH. |
LogRecord |
Location.traceThrowable(int severity,
MsgObject msgObject,
Object[] args,
Throwable exc)
Trace message with stack trace of given exception, into this loaction. |
LogRecord |
Location.traceThrowable(int severity,
MsgObject msgObject,
Throwable exc)
Trace message with stack trace of given exception, into this location. |
LogRecord |
Location.traceThrowable(int severity,
String subloc,
MsgObject msgObject,
Object[] args,
Throwable exc)
Trace message with stack trace of given exception, into this location. |
LogRecord |
Location.traceThrowable(int severity,
String subloc,
MsgObject msgObject,
Throwable exc)
Trace message with stack trace of given exception, into this location. |
LogRecord |
Location.warning(Category[] categories,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category[] categories,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category[] categories,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category[] categories,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category category,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category category,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category category,
String subloc,
MsgObject msgObject)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Location.warning(Category category,
String subloc,
MsgObject msgObject,
Object[] args)
Deprecated. Logging to a Category from Location context is not proper. If you want the message to appear both in traces and logs, use Category and pass a Location parameter or issue separate calls to a Location and a Category parameter |
LogRecord |
Category.warning(Location loc,
MsgObject msgObject)
Same as Category.log(int,
Location,
MsgObject)
but always emits an warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Category.warning(Location loc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
MsgObject,
java.lang.Object[])
but always emits an warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Category.warning(Location loc,
String subLoc,
MsgObject msgObject)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject)
but always emits an warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Category.warning(Location loc,
String subLoc,
MsgObject msgObject,
Object[] args)
Same as Category.log(int,
Location,
java.lang.String,
MsgObject,
java.lang.Object[])
but always emits an warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Location.warning(MsgObject msgObject)
Same as Location.log(int,
com.sap.tc.logging.MsgObject)
but always emits a warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Location.warning(MsgObject msgObject,
Object[] args)
Same as Location.log(int,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Location.warning(String subloc,
MsgObject msgObject)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject)
but always emits a warning message, that is a message of severity
Severity.WARNING. |
LogRecord |
Location.warning(String subloc,
MsgObject msgObject,
Object[] args)
Same as Location.log(int,
java.lang.String,
com.sap.tc.logging.MsgObject,
java.lang.Object[])
but always emits a warning message, that is a message of severity
Severity.WARNING. |
|
SAP NetWeaver 7.20 (SP01) Composition Environment | |||||||||
| PREV NEXT | FRAMES NO FRAMES | |||||||||