• 卓帕卡布拉动作/冒险Windows/Linux/Macintosh 2018-12-12
  • 使命召唤15:黑色行动4windows 2018-12-12
  • “地才”的他们崛起,证明努力绝对是件好事 2018-12-12
  • 扶贫领域腐败问题督查:乡干部成了“包工头”? 2018-12-12
  • #游戏江湖事#政确选黑,玩家选白,游戏公司应当站哪边?瓦克五1226 2018-12-12
  • 大神活动网易炉石大神计划启动 2018-12-12
  • 新游前瞻玩家的饕餮盛宴!2018年全平台必玩游戏推荐!(中) 2018-12-12
  • 林郑月娥:香港不会改变自由贸易的重要地位 2018-12-12
  • 兔子角斗士动作/冒险Windows 2018-12-12
  • 圣兽助战《梦幻西游》手游九黎之墟帮派守护兽解锁 2018-12-12
  • 中日交易所签署备忘录助推中日ETF实现互通 2018-12-12
  • 《七人传奇:英雄集结》公测卡 2018-12-12
  • 暗黑“3”分钟第一期:猎魔人天下第一火多重 2018-12-12
  • 感恩节马赛克拼图解谜Windows/Macintosh 2018-12-12
  • 使命召唤15:黑色行动4windows 2018-12-12
  • The Jar Scanner Component

    Table of Contents

    Introduction

    新开户送体验金68 www.oneworldfilmnet.com The Jar Scanner element represents the component that is used to scan the web application for JAR files and directories of class files. It is typically used during web application start to identify configuration files such as TLDs or web-fragment.xml files that must be processed as part of the web application initialisation.

    A Jar Scanner element MAY be nested inside a Context component.

    For example you can include the bootstrap classpath when scanning for jar files:

    <Context>
      ...
      <JarScanner scanBootstrapClassPath="true"/>
      ...
    </Context>

    If a Jar Scanner element is not included, a default Jar Scanner configuration will be created automatically, which is sufficient for most requirements.

    Attributes

    Common Attributes

    All implementations of Jar Scanner support the following attributes:

    Attribute Description
    className

    Java class name of the implementation to use. This class must implement the org.apache.tomcat.JarScanner interface. If not specified, the standard value (defined below) will be used.

    Standard Implementation

    The standard implementation of Jar Scanner is org.apache.tomcat.util.scan.StandardJarScanner. It supports the following additional attributes (in addition to the common attributes listed above):

    Attribute Description
    scanAllDirectories

    If true, any directories found on the classpath will be checked to see if they are expanded JAR files. The default is false.

    Tomcat determines if a directory is an expanded JAR file by looking for a META-INF sub-directory. Only if the META-INF sub-directory exists, the directory is assumed to be an expanded JAR file. Note that for scans for matches to @HandlesTypes annotations, all directories will be scanned irrespective of the presence or not of a META-INF sub-directory.

    scanAllFiles

    If true, any files found on the classpath will be checked to see if they are Jar files rather than relying on the file extension being .jar. The default is false.

    scanClassPath

    If true, the full web application classpath, including the shared and common classloaders and the system classpath (but not the bootstrap classpath) will be scanned for Jar files in addition to the web application. The default is true.

    scanBootstrapClassPath

    If scanClassPath is true and this is true the bootstrap classpath will also be scanned for Jar files. The default is false.

    scanManifest

    If true, the Manifest files of any JARs found will be scanned for additional class path entries and those entries will be added to the URLs to scan. The default is true.

    Nested Components

    Only a Jar Scan Filter may be nested inside a Jar Scanner element.

    Special Features

    No special features are associated with a Jar Scanner element.

    Comments

    Notice: This comments section collects your suggestions on improving documentation for Apache Tomcat.

    If you have trouble and need help, read Find Help page and ask your question on the tomcat-users 新开户送体验金68. Do not ask such questions here. This is not a Q&A section.

    The Apache Comments System is explained here. Comments may be removed by our moderators if they are either implemented or considered invalid/off-topic.

  • 新开户送体验金68
  • 投哪网如何使用现金券
  • 外汇平台开户送体验金
  • 乐虎国际手机平台 | 旋乐吧spin8 | 利来在线 | 利来app | 高博亚洲 |