亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频

? 歡迎來到蟲蟲下載站! | ?? 資源下載 ?? 資源專輯 ?? 關于我們
? 蟲蟲下載站

?? handler.java

?? linux下編程用 編譯軟件
?? JAVA
字號:
/* Handler.java -- a class for publishing log messages   Copyright (C) 2002, 2004 Free Software Foundation, Inc.This file is part of GNU Classpath.GNU Classpath is free software; you can redistribute it and/or modifyit under the terms of the GNU General Public License as published bythe Free Software Foundation; either version 2, or (at your option)any later version.GNU Classpath is distributed in the hope that it will be useful, butWITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNUGeneral Public License for more details.You should have received a copy of the GNU General Public Licensealong with GNU Classpath; see the file COPYING.  If not, write to theFree Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA02110-1301 USA.Linking this library statically or dynamically with other modules ismaking a combined work based on this library.  Thus, the terms andconditions of the GNU General Public License cover the wholecombination.As a special exception, the copyright holders of this library give youpermission to link this library with independent modules to produce anexecutable, regardless of the license terms of these independentmodules, and to copy and distribute the resulting executable underterms of your choice, provided that you also meet, for each linkedindependent module, the terms and conditions of the license of thatmodule.  An independent module is a module which is not derived fromor based on this library.  If you modify this library, you may extendthis exception to your version of the library, but you are notobligated to do so.  If you do not wish to do so, delete thisexception statement from your version. */package java.util.logging;import java.io.UnsupportedEncodingException;/** * A <code>Handler</code> publishes <code>LogRecords</code> to * a sink, for example a file, the console or a network socket. * There are different subclasses of <code>Handler</code> * to deal with different kinds of sinks. * * <p>FIXME: Are handlers thread-safe, or is the assumption that only * loggers are, and a handler can belong only to one single logger? If * the latter, should we enforce it? (Spec not clear). In any * case, it needs documentation. * * @author Sascha Brawer (brawer@acm.org) */public abstract class Handler{  Formatter     formatter;  Filter        filter;  Level         level;  ErrorManager  errorManager;  String        encoding;  /**   * Constructs a Handler with a logging severity level of   * <code>Level.ALL</code>, no formatter, no filter, and   * an instance of <code>ErrorManager</code> managing errors.   *   * <p><strong>Specification Note:</strong> The specification of the   * Java<sup>TM</sup> Logging API does not mention which character   * encoding is to be used by freshly constructed Handlers.  The GNU   * implementation uses the default platform encoding, but other   * Java implementations might behave differently.   *   * <p><strong>Specification Note:</strong> While a freshly constructed   * Handler is required to have <em>no filter</em> according to the   * specification, <code>null</code> is not a valid parameter for   * <code>Handler.setFormatter</code>.  Therefore, the following   * code will throw a <code>java.lang.NullPointerException</code>:   *   * <p><pre>Handler h = new MyConcreteSubclassOfHandler();h.setFormatter(h.getFormatter());</pre>   *   * It seems strange that a freshly constructed Handler is not   * supposed to provide a Formatter, but this is what the specification   * says.   */  protected Handler()  {    level = Level.ALL;  }  /**   * Publishes a <code>LogRecord</code> to an appropriate sink,   * provided the record passes all tests for being loggable.  The   * <code>Handler</code> will localize the message of the log   * record and substitute any message parameters.   *   * <p>Most applications do not need to call this method directly.   * Instead, they will use use a {@link Logger}, which will   * create LogRecords and distribute them to registered handlers.   *   * <p>In case of an I/O failure, the <code>ErrorManager</code>   * of this <code>Handler</code> will be informed, but the caller   * of this method will not receive an exception.   *   * @param record the log event to be published.   */  public abstract void publish(LogRecord record);  /**   * Forces any data that may have been buffered to the underlying   * output device.   *   * <p>In case of an I/O failure, the <code>ErrorManager</code>   * of this <code>Handler</code> will be informed, but the caller   * of this method will not receive an exception.   */  public abstract void flush();  /**   * Closes this <code>Handler</code> after having flushed   * the buffers.  As soon as <code>close</code> has been called,   * a <code>Handler</code> should not be used anymore. Attempts   * to publish log records, to flush buffers, or to modify the   * <code>Handler</code> in any other way may throw runtime   * exceptions after calling <code>close</code>.   *   * <p>In case of an I/O failure, the <code>ErrorManager</code>   * of this <code>Handler</code> will be informed, but the caller   * of this method will not receive an exception.   *   * @throws SecurityException if a security manager exists and   *         the caller is not granted the permission to control   *         the logging infrastructure.   */  public abstract void close()    throws SecurityException;  /**   * Returns the <code>Formatter</code> which will be used to   * localize the text of log messages and to substitute   * message parameters.  A <code>Handler</code> is encouraged,   * but not required to actually use an assigned   * <code>Formatter</code>.   *   * @return the <code>Formatter</code> being used, or   *         <code>null</code> if this <code>Handler</code>   *         does not use formatters and no formatter has   *         ever been set by calling <code>setFormatter</code>.   */  public Formatter getFormatter()  {    return formatter;  }  /**   * Sets the <code>Formatter</code> which will be used to   * localize the text of log messages and to substitute   * message parameters.  A <code>Handler</code> is encouraged,   * but not required to actually use an assigned   * <code>Formatter</code>.   *   * @param formatter the new <code>Formatter</code> to use.   *   * @throws SecurityException if a security manager exists and   *         the caller is not granted the permission to control   *         the logging infrastructure.   *   * @throws NullPointerException if <code>formatter</code> is   *         <code>null</code>.   */  public void setFormatter(Formatter formatter)    throws SecurityException  {    LogManager.getLogManager().checkAccess();        /* Throws a NullPointerException if formatter is null. */    formatter.getClass();    this.formatter = formatter;  }  /**   * Returns the character encoding which this handler uses for publishing   * log records.   *   * @return the name of a character encoding, or <code>null</code>   *         for the default platform encoding.   */  public String getEncoding()  {    return encoding;  }  /**   * Sets the character encoding which this handler uses for publishing   * log records.  The encoding of a <code>Handler</code> must be   * set before any log records have been published.   *   * @param encoding the name of a character encoding, or <code>null</code>   *            for the default encoding.   *   * @exception SecurityException if a security manager exists and   *            the caller is not granted the permission to control   *            the logging infrastructure.   *   */  public void setEncoding(String encoding)    throws SecurityException, UnsupportedEncodingException  {    /* Should any developer ever change this implementation, they are     * advised to have a look at StreamHandler.setEncoding(String),     * which overrides this method without calling super.setEncoding.     */    LogManager.getLogManager().checkAccess();    /* Simple check for supported encodings. This is more expensive     * than it could be, but this method is overwritten by StreamHandler     * anyway.     */    if (encoding != null)      new String(new byte[0], encoding);    this.encoding = encoding;  }  /**   * Returns the <code>Filter</code> that currently controls which   * log records are being published by this <code>Handler</code>.   *   * @return the currently active <code>Filter</code>, or   *         <code>null</code> if no filter has been associated.   *         In the latter case, log records are filtered purely   *         based on their severity level.   */  public Filter getFilter()  {    return filter;  }  /**   * Sets the <code>Filter</code> for controlling which   * log records will be published by this <code>Handler</code>.   *   * @param filter the <code>Filter</code> to use, or   *         <code>null</code> to filter log records purely based   *         on their severity level.   */  public void setFilter(Filter filter)    throws SecurityException  {    LogManager.getLogManager().checkAccess();    this.filter = filter;  }  /**   * Returns the <code>ErrorManager</code> that currently deals   * with errors originating from this Handler.   *   * @exception SecurityException if a security manager exists and   *            the caller is not granted the permission to control   *            the logging infrastructure.   */  public ErrorManager getErrorManager()  {    LogManager.getLogManager().checkAccess();    /* Developers wanting to change the subsequent code should     * have a look at Handler.reportError -- it also can create     * an ErrorManager, but does so without checking permissions     * to control the logging infrastructure.     */    if (errorManager == null)      errorManager = new ErrorManager();    return errorManager;  }  public void setErrorManager(ErrorManager manager)  {    LogManager.getLogManager().checkAccess();    /* Make sure manager is not null. */    manager.getClass();    this.errorManager = manager;  }  protected void reportError(String message, Exception ex, int code)  {    if (errorManager == null)      errorManager = new ErrorManager();    errorManager.error(message, ex, code);  }  /**   * Returns the severity level threshold for this <code>Handler</code>   * All log records with a lower severity level will be discarded;   * a log record of the same or a higher level will be published   * unless an installed <code>Filter</code> decides to discard it.   *   * @return the severity level below which all log messages   *         will be discarded.   */  public Level getLevel()  {    return level;  }  /**   * Sets the severity level threshold for this <code>Handler</code>.   * All log records with a lower severity level will be discarded;   * a log record of the same or a higher level will be published   * unless an installed <code>Filter</code> decides to discard it.   *   * @param level the severity level below which all log messages   *              will be discarded.   *   * @exception SecurityException if a security manager exists and   *            the caller is not granted the permission to control   *            the logging infrastructure.   *   * @exception NullPointerException if <code>level</code> is   *            <code>null</code>.   */  public void setLevel(Level level)  {    LogManager.getLogManager().checkAccess();    /* Throw NullPointerException if level is null.  */    level.getClass();    this.level = level;  }  /**   * Checks whether a <code>LogRecord</code> would be logged   * if it was passed to this <code>Handler</code> for publication.   *   * <p>The <code>Handler</code> implementation considers a record as   * loggable if its level is greater than or equal to the severity   * level threshold.  In a second step, if a {@link Filter} has   * been installed, its {@link Filter#isLoggable(LogRecord) isLoggable}   * method is invoked. Subclasses of <code>Handler</code> can override   * this method to impose their own constraints.   *   * @param record the <code>LogRecord</code> to be checked.   *   * @return <code>true</code> if <code>record</code> would   *         be published by {@link #publish(LogRecord) publish},   *         <code>false</code> if it would be discarded.   *   * @see #setLevel(Level)   * @see #setFilter(Filter)   * @see Filter#isLoggable(LogRecord)   *   * @throws NullPointerException if <code>record</code>   *         is <code>null</code>.   */  public boolean isLoggable(LogRecord record)  {    if (record.getLevel().intValue() < level.intValue())      return false;        if (filter != null)      return filter.isLoggable(record);    else      return true;  }}

?? 快捷鍵說明

復制代碼 Ctrl + C
搜索代碼 Ctrl + F
全屏模式 F11
切換主題 Ctrl + Shift + D
顯示快捷鍵 ?
增大字號 Ctrl + =
減小字號 Ctrl + -
亚洲欧美第一页_禁久久精品乱码_粉嫩av一区二区三区免费野_久草精品视频
亚洲一级二级三级在线免费观看| 国产午夜精品久久久久久久 | 精品国产第一区二区三区观看体验| 91久久精品一区二区二区| 不卡视频一二三四| 成人av免费在线| 91麻豆精品在线观看| 色老头久久综合| 欧美在线一区二区| 91.com视频| 日韩限制级电影在线观看| 欧美不卡一区二区| 在线不卡欧美精品一区二区三区| 欧美精品在线观看一区二区| 91国在线观看| 色偷偷88欧美精品久久久| 在线视频一区二区三| 欧美色图片你懂的| 欧美变态口味重另类| 精品国产乱码久久久久久免费| 成人精品国产一区二区4080| 91蜜桃网址入口| 91精品国产色综合久久不卡蜜臀 | 成人午夜精品一区二区三区| 91在线视频官网| 制服视频三区第一页精品| 精品精品欲导航| 中文字幕一区二区三区四区 | 亚洲三级在线观看| 日日摸夜夜添夜夜添亚洲女人| 国内精品国产成人国产三级粉色 | 成人av综合在线| 精品视频1区2区| 国产午夜三级一区二区三| 亚洲欧美日韩电影| 久久精品国产亚洲高清剧情介绍| 99久久久国产精品| 精品捆绑美女sm三区| 亚洲精品大片www| 国产成人一区在线| 日韩视频永久免费| 亚洲欧美日韩中文字幕一区二区三区| 日韩二区在线观看| 一本一道久久a久久精品| 精品捆绑美女sm三区| 亚洲不卡一区二区三区| 成人综合婷婷国产精品久久| 91麻豆精品国产91久久久久久久久| 国产精品乱码一区二区三区软件| 日韩va欧美va亚洲va久久| 国产精选一区二区三区| 欧美日韩免费观看一区三区| 国产精品午夜春色av| 蜜桃av噜噜一区| 不卡av在线免费观看| 日韩片之四级片| 亚洲国产中文字幕在线视频综合| 韩国女主播成人在线| 欧美日韩激情一区二区三区| 欧美国产日韩在线观看| 国产在线精品国自产拍免费| 欧美丰满少妇xxxxx高潮对白| 亚洲日本va在线观看| 国产91在线看| 国产欧美日韩不卡免费| 日本亚洲欧美天堂免费| 91国偷自产一区二区开放时间| 久久久国产午夜精品| 男女男精品视频| 欧美一区二区三区免费大片 | 国产视频亚洲色图| 国内成人精品2018免费看| 欧美成人vr18sexvr| 久久99精品网久久| 欧美成人免费网站| 麻豆精品在线视频| 日韩写真欧美这视频| 首页欧美精品中文字幕| 正在播放亚洲一区| 午夜日韩在线电影| 色婷婷综合视频在线观看| 亚洲六月丁香色婷婷综合久久| 99视频精品在线| 亚洲综合免费观看高清完整版在线| 成人av午夜电影| 欧美国产激情一区二区三区蜜月| 成人黄动漫网站免费app| 国产精品久久国产精麻豆99网站| 高清久久久久久| 中文字幕亚洲精品在线观看| 成人av午夜影院| 亚洲精品日产精品乱码不卡| 在线免费观看日韩欧美| 丝袜亚洲另类欧美综合| 精品国产成人在线影院| 国产乱码精品一区二区三区五月婷| 国产日韩三级在线| 欧美亚洲综合网| 久久se精品一区精品二区| 久久久久久久久久久久久夜| 91黄色在线观看| 久久国产精品72免费观看| 国产精品午夜免费| 91精品在线观看入口| 国产高清精品在线| 午夜欧美在线一二页| 久久品道一品道久久精品| 色94色欧美sute亚洲线路一久| 日韩国产成人精品| 中文字幕在线观看一区| 欧美日韩精品一区二区| 国产乱理伦片在线观看夜一区| 亚洲免费在线视频| 日韩欧美中文一区二区| 99久久99久久精品国产片果冻 | 国产精品99久久久久久似苏梦涵 | 精品免费一区二区三区| av亚洲精华国产精华| 日本三级韩国三级欧美三级| 亚洲日本丝袜连裤袜办公室| 日韩精品中文字幕在线不卡尤物| 色综合天天天天做夜夜夜夜做| 另类的小说在线视频另类成人小视频在线 | 国产成人综合视频| 天堂va蜜桃一区二区三区漫画版| 国产欧美日本一区二区三区| 7777精品伊人久久久大香线蕉经典版下载 | 偷拍自拍另类欧美| 国产精品久久久久久久裸模 | 亚洲男女一区二区三区| 久久久久九九视频| 欧美电影免费观看完整版| 欧美色图一区二区三区| 99精品久久久久久| 成人久久视频在线观看| 美国十次综合导航| 日本欧美在线看| 亚洲在线观看免费视频| 亚洲欧洲av在线| 久久久亚洲午夜电影| 日韩一区二区三区视频在线观看 | 久久精品久久99精品久久| 亚洲亚洲人成综合网络| 日韩毛片在线免费观看| 91免费看视频| 亚洲国产成人自拍| 欧美极品美女视频| 久久午夜电影网| 久久先锋影音av| 久久五月婷婷丁香社区| 日韩视频免费观看高清完整版在线观看 | 欧美videossexotv100| 91精品在线观看入口| 欧美日本精品一区二区三区| 欧美日韩视频在线观看一区二区三区| 成人a免费在线看| 成人av中文字幕| 91蝌蚪porny| 91免费在线看| 日本精品视频一区二区| 91福利视频网站| 欧美日韩在线三区| 欧美久久高跟鞋激| 91精品国产高清一区二区三区蜜臀 | 春色校园综合激情亚洲| 成人app软件下载大全免费| 99综合电影在线视频| 不卡免费追剧大全电视剧网站| 成人美女视频在线观看| 色天天综合色天天久久| 欧美日韩黄色一区二区| 91精品国产综合久久香蕉的特点| 精品久久一二三区| 一区在线观看免费| 五月激情综合婷婷| 国产露脸91国语对白| 91麻豆文化传媒在线观看| 欧美人牲a欧美精品| 国产午夜三级一区二区三| 亚洲人123区| 免费成人你懂的| 99久久久国产精品免费蜜臀| 欧美视频在线观看一区二区| www国产成人| 亚洲精品日韩综合观看成人91| 男人的天堂久久精品| eeuss鲁片一区二区三区在线观看| 色狠狠桃花综合| 久久在线观看免费| 一区二区视频在线| 国产在线麻豆精品观看| 91福利在线免费观看| 精品国产污污免费网站入口| 一区二区在线免费观看| 国产精品18久久久久久久久久久久 | 99这里只有久久精品视频| 日韩一级片网址| 亚洲码国产岛国毛片在线| 久久国产乱子精品免费女| 91在线云播放|