web-app_2_5.xsd

业界著名的tomcat服务器的最新6.0的源代码。

                minOccurs="0" maxOccurs="unbounded" />
        </xsd:sequence>
        <xsd:attribute name="id" type="xsd:ID" />
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="auth-methodType">
        <xsd:annotation>
            <xsd:documentation>
                The auth-methodType is used to configure the
                authentication mechanism for the web application. As a
                prerequisite to gaining access to any web resources
                which are protected by an authorization constraint, a
                user must have authenticated using the configured
                mechanism. Legal values are "BASIC", "DIGEST", "FORM",
                "CLIENT-CERT", or a vendor-specific authentication
                scheme. Used in: login-config
            </xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:restriction base="javaee:string" />
        </xsd:simpleContent>
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="dispatcherType">
        <xsd:annotation>
            <xsd:documentation>
                The dispatcher has four legal values: FORWARD, REQUEST,
                INCLUDE, and ERROR. A value of FORWARD means the Filter
                will be applied under RequestDispatcher.forward() calls.
                A value of REQUEST means the Filter will be applied
                under ordinary client calls to the path or servlet. A
                value of INCLUDE means the Filter will be applied under
                RequestDispatcher.include() calls. A value of ERROR
                means the Filter will be applied under the error page
                mechanism. The absence of any dispatcher elements in a
                filter-mapping indicates a default of applying filters
                only under ordinary client calls to the path or servlet.
            </xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:restriction base="javaee:string">
                <xsd:enumeration value="FORWARD" />
                <xsd:enumeration value="INCLUDE" />
                <xsd:enumeration value="REQUEST" />
                <xsd:enumeration value="ERROR" />
            </xsd:restriction>
        </xsd:simpleContent>
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:simpleType name="encodingType">
        <xsd:annotation>
            <xsd:documentation>
                The encodingType defines IANA character sets.
            </xsd:documentation>
        </xsd:annotation>
        <xsd:restriction base="xsd:string">
            <xsd:pattern value="[^\s]+" />
        </xsd:restriction>
    </xsd:simpleType>
    <!-- **************************************************** -->
    <xsd:complexType name="error-codeType">
        <xsd:annotation>
            <xsd:documentation>
                The error-code contains an HTTP error code, ex: 404 Used
                in: error-page
            </xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:restriction base="javaee:xsdPositiveIntegerType">
                <xsd:pattern value="\d{3}" />
                <xsd:attribute name="id" type="xsd:ID" />
            </xsd:restriction>
        </xsd:simpleContent>
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="error-pageType">
        <xsd:annotation>
            <xsd:documentation>
                The error-pageType contains a mapping between an error
                code or exception type to the path of a resource in the
                web application. Used in: web-app
            </xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:choice>
                <xsd:element name="error-code"
                    type="javaee:error-codeType" />
                <xsd:element name="exception-type"
                    type="javaee:fully-qualified-classType">
                    <xsd:annotation>
                        <xsd:documentation>
                            The exception-type contains a fully
                            qualified class name of a Java exception
                            type.
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:element>
            </xsd:choice>
            <xsd:element name="location" type="javaee:war-pathType">
                <xsd:annotation>
                    <xsd:documentation>
                        The location element contains the location of
                        the resource in the web application relative to
                        the root of the web application. The value of
                        the location must have a leading `/'.
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="id" type="xsd:ID" />
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="filter-mappingType">
        <xsd:annotation>
            <xsd:documentation>
                Declaration of the filter mappings in this web
                application is done by using filter-mappingType. The
                container uses the filter-mapping declarations to decide
                which filters to apply to a request, and in what order.
                The container matches the request URI to a Servlet in
                the normal way. To determine which filters to apply it
                matches filter-mapping declarations either on
                servlet-name, or on url-pattern for each filter-mapping
                element, depending on which style is used. The order in
                which filters are invoked is the order in which
                filter-mapping declarations that match a request URI for
                a servlet appear in the list of filter-mapping
                elements.The filter-name value must be the value of the
                filter-name sub-elements of one of the filter
                declarations in the deployment descriptor.
            </xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:element name="filter-name"
                type="javaee:filter-nameType" />
            <xsd:choice minOccurs="1" maxOccurs="unbounded">
                <xsd:element name="url-pattern"
                    type="javaee:url-patternType" />
                <xsd:element name="servlet-name"
                    type="javaee:servlet-nameType" />
            </xsd:choice>
            <xsd:element name="dispatcher" type="javaee:dispatcherType"
                minOccurs="0" maxOccurs="4" />
        </xsd:sequence>
        <xsd:attribute name="id" type="xsd:ID" />
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="filter-nameType">
        <xsd:annotation>
            <xsd:documentation>
                The logical name of the filter is declare by using
                filter-nameType. This name is used to map the filter.
                Each filter name is unique within the web application.
                Used in: filter, filter-mapping
            </xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:extension base="javaee:nonEmptyStringType" />
        </xsd:simpleContent>
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="filterType">
        <xsd:annotation>
            <xsd:documentation>
                The filterType is used to declare a filter in the web
                application. The filter is mapped to either a servlet or
                a URL pattern in the filter-mapping element, using the
                filter-name value to reference. Filters can access the
                initialization parameters declared in the deployment
                descriptor at runtime via the FilterConfig interface.
                Used in: web-app
            </xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:group ref="javaee:descriptionGroup" />
            <xsd:element name="filter-name"
                type="javaee:filter-nameType" />
            <xsd:element name="filter-class"
                type="javaee:fully-qualified-classType">
                <xsd:annotation>
                    <xsd:documentation>
                        The fully qualified classname of the filter.
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:element>
            <xsd:element name="init-param" type="javaee:param-valueType"
                minOccurs="0" maxOccurs="unbounded">
                <xsd:annotation>
                    <xsd:documentation>
                        The init-param element contains a name/value
                        pair as an initialization param of a servlet
                        filter
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="id" type="xsd:ID" />
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:complexType name="form-login-configType">
        <xsd:annotation>
            <xsd:documentation>
                The form-login-configType specifies the login and error
                pages that should be used in form based login. If form
                based authentication is not used, these elements are
                ignored. Used in: login-config
            </xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:element name="form-login-page"
                type="javaee:war-pathType">
                <xsd:annotation>
                    <xsd:documentation>
                        The form-login-page element defines the location
                        in the web app where the page that can be used
                        for login can be found. The path begins with a
                        leading / and is interpreted relative to the
                        root of the WAR.
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:element>
            <xsd:element name="form-error-page"
                type="javaee:war-pathType">
                <xsd:annotation>
                    <xsd:documentation>
                        The form-error-page element defines the location
                        in the web app where the error page that is
                        displayed when login is not successful can be
                        found. The path begins with a leading / and is
                        interpreted relative to the root of the WAR.
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="id" type="xsd:ID" />
    </xsd:complexType>
    <!-- **************************************************** -->
    <xsd:simpleType name="鈥?http-methodType鈥?">