设为首页 收藏本站
查看: 429|回复: 0

[经验分享] org.apache.juli.logging.Log

[复制链接]

尚未签到

发表于 2015-8-6 09:52:11 | 显示全部楼层 |阅读模式
package org.apache.juli.logging;
/**
* 日志接口API。为了能够被LogFactory实例,实现这个Log接口的类必须要包含
* 含有单个字符串作为参数的构造函数,这个字符串参数用来作为日志的名字。
* Log含有6个日志级别:
* trace
* debug
* info
* warn
* error
* fatal
*
* The mapping of these log levels to the concepts used by the underlying
* logging system is implementation dependent.
* The implementation should ensure, though, that this ordering behaves
* as expected.
*
* Performance is often a logging concern.
* By examining the appropriate property,
* a component can avoid expensive operations (producing information
* to be logged).
*
*  For example,
*
*    if (log.isDebugEnabled()) {
*        ... do something expensive ...
*        log.debug(theResult);
*    }
*
*
*
* Configuration of the underlying logging system will generally be done
* external to the Logging APIs, through whatever mechanism is supported by
* that system.
*
* @author Scott Sanders
* @author Rod Waldhoff
*/
public interface Log {

// ----------------------------------------------------- Logging Properties

/**
*  Is debug logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than debug.
*/
public boolean isDebugEnabled();

/**
*  Is error logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than error.
*/
public boolean isErrorEnabled();

/**
*  Is fatal logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than fatal.
*/
public boolean isFatalEnabled();

/**
*  Is info logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than info.
*/
public boolean isInfoEnabled();

/**
*  Is trace logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than trace.
*/
public boolean isTraceEnabled();

/**
*  Is warn logging currently enabled?
*
*  Call this method to prevent having to perform expensive operations
* (for example, String concatenation)
* when the log level is more than warn.
*/
public boolean isWarnEnabled();

// -------------------------------------------------------- Logging Methods

/**
*  Log a message with trace log level.
*
* @param message log this message
*/
public void trace(Object message);

/**
*  Log an error with trace log level.
*
* @param message log this message
* @param t log this cause
*/
public void trace(Object message, Throwable t);

/**
*  Log a message with debug log level.
*
* @param message log this message
*/
public void debug(Object message);

/**
*  Log an error with debug log level.
*
* @param message log this message
* @param t log this cause
*/
public void debug(Object message, Throwable t);

/**
*  Log a message with info log level.
*
* @param message log this message
*/
public void info(Object message);

/**
*  Log an error with info log level.
*
* @param message log this message
* @param t log this cause
*/
public void info(Object message, Throwable t);

/**
*  Log a message with warn log level.
*
* @param message log this message
*/
public void warn(Object message);

/**
*  Log an error with warn log level.
*
* @param message log this message
* @param t log this cause
*/
public void warn(Object message, Throwable t);

/**
*  Log a message with error log level.
*
* @param message log this message
*/
public void error(Object message);

/**
*  Log an error with error log level.
*
* @param message log this message
* @param t log this cause
*/
public void error(Object message, Throwable t);

/**
*  Log a message with fatal log level.
*
* @param message log this message
*/
public void fatal(Object message);

/**
*  Log an error with fatal log level.
*
* @param message log this message
* @param t log this cause
*/
public void fatal(Object message, Throwable t);

}
  
  

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-94629-1-1.html 上篇帖子: Apache Shiro 学习记录3 下篇帖子: Apache InterfaceAudience
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表