• Introduction
• Attributes
  1. Common Attributes
  2. Standard Implementation
• Nested Components
• Special Features

The Jar Scanner element represents the component that is used to scan the web application for JAR 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. If it is not included, a default Jar Scanner configuration will be created automatically, which is sufficient for most requirements.

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 scanClassPath If true, the full web application classpath, including the shared and common classloaders will be scanned for Jar files in addition to the web application. The default is true. 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 scanAllDirectories If true, any directories found on the classpath will be checked to see if are expanded Jar files. The default is false. Tomcat determines if directory is an expanded JAR file by looking for a META-INF sub-directory. Only if the META-INF sub-directory exists, is the directory to be an expanded JAR file.

No components may be nested inside a Jar Scanner element.

No special features are associated with a Jar Scanner element.