web-app_2_5.xsd

梅花雪树的经典制作

<?xml version="1.0" encoding="UTF-8"?>
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://java.sun.com/xml/ns/javaee"
    xmlns:javaee="http://java.sun.com/xml/ns/javaee"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified" attributeFormDefault="unqualified"
    version="2.5">
    <xsd:annotation>
        <xsd:documentation>
            @(#)web-app_2_5.xsds1.62 05/08/06
        </xsd:documentation>
    </xsd:annotation>
    <xsd:annotation>
        <xsd:documentation>
            <![CDATA[
      This is the XML Schema for the Servlet 2.5 deployment descriptor. 
The deployment descriptor must be named "WEB-INF/web.xml" in the 
web application's war file.  All Servlet deployment descriptors 
must indicate the web application schema by using the Java EE 
namespace: 
http://java.sun.com/xml/ns/javaee 
and by indicating the version of the schema by 
using the version element as shown below: 
    <web-app xmlns="http://java.sun.com/xml/ns/javaee" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xsi:schemaLocation="..." 
      version="2.5"> 
      ... 
    </web-app> 
The instance documents may indicate the published version of 
the schema using the xsi:schemaLocation attribute for Java EE 
namespace with the following location: 
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd 
]]>
        </xsd:documentation>
    </xsd:annotation>
    <xsd:annotation>
        <xsd:documentation>
            The following conventions apply to all Java EE deployment
            descriptor elements unless indicated otherwise. - In
            elements that specify a pathname to a file within the same
            JAR file, relative filenames (i.e., those not starting with
            "/") are considered relative to the root of the JAR file's
            namespace. Absolute filenames (i.e., those starting with
            "/") also specify names in the root of the JAR file's
            namespace. In general, relative names are preferred. The
            exception is .war files where absolute names are preferred
            for consistency with the Servlet API.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:include schemaLocation="javaee_5.xsd" />
    <xsd:include schemaLocation="jsp_2_1.xsd" />
    <!-- **************************************************** -->
    <xsd:element name="web-app" type="javaee:web-appType">
        <xsd:annotation>
            <xsd:documentation>
                The web-app element is the root of the deployment
                descriptor for a web application. Note that the
                sub-elements of this element can be in the arbitrary
                order. Because of that, the multiplicity of the elements
                of distributable, session-config, welcome-file-list,
                jsp-config, login-config, and
                locale-encoding-mapping-list was changed from "?" to "*"
                in this schema. However, the deployment descriptor
                instance file must not contain multiple elements of
                session-config, jsp-config, and login-config. When there
                are multiple elements of welcome-file-list or
                locale-encoding-mapping-list, the container must
                concatenate the element contents. The multiple occurence
                of the element distributable is redundant and the
                container treats that case exactly in the same way when
                there is only one distributable.
            </xsd:documentation>
        </xsd:annotation>
        <xsd:unique name="web-app-servlet-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The servlet element contains the name of a servlet.
                    The name must be unique within the web application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:servlet" />
            <xsd:field xpath="javaee:servlet-name" />
        </xsd:unique>
        <xsd:unique name="web-app-filter-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The filter element contains the name of a filter.
                    The name must be unique within the web application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:filter" />
            <xsd:field xpath="javaee:filter-name" />
        </xsd:unique>
        <xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The ejb-local-ref-name element contains the name of
                    an EJB reference. The EJB reference is an entry in
                    the web application's environment and is relative to
                    the java:comp/env context. The name must be unique
                    within the web application. It is recommended that
                    name is prefixed with "ejb/".
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:ejb-local-ref" />
            <xsd:field xpath="javaee:ejb-ref-name" />
        </xsd:unique>
        <xsd:unique name="web-app-ejb-ref-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The ejb-ref-name element contains the name of an EJB
                    reference. The EJB reference is an entry in the web
                    application's environment and is relative to the
                    java:comp/env context. The name must be unique
                    within the web application. It is recommended that
                    name is prefixed with "ejb/".
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:ejb-ref" />
            <xsd:field xpath="javaee:ejb-ref-name" />
        </xsd:unique>
        <xsd:unique name="web-app-resource-env-ref-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The resource-env-ref-name element specifies the name
                    of a resource environment reference; its value is
                    the environment entry name used in the web
                    application code. The name is a JNDI name relative
                    to the java:comp/env context and must be unique
                    within a web application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:resource-env-ref" />
            <xsd:field xpath="javaee:resource-env-ref-name" />
        </xsd:unique>
        <xsd:unique name="web-app-message-destination-ref-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The message-destination-ref-name element specifies
                    the name of a message destination reference; its
                    value is the environment entry name used in the web
                    application code. The name is a JNDI name relative
                    to the java:comp/env context and must be unique
                    within a web application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:message-destination-ref" />
            <xsd:field xpath="javaee:message-destination-ref-name" />
        </xsd:unique>
        <xsd:unique name="web-app-res-ref-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The res-ref-name element specifies the name of a
                    resource manager connection factory reference. The
                    name is a JNDI name relative to the java:comp/env
                    context. The name must be unique within a web
                    application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:resource-ref" />
            <xsd:field xpath="javaee:res-ref-name" />
        </xsd:unique>
        <xsd:unique name="web-app-env-entry-name-uniqueness">
            <xsd:annotation>
                <xsd:documentation>
                    The env-entry-name element contains the name of a
                    web application's environment entry. The name is a
                    JNDI name relative to the java:comp/env context. The
                    name must be unique within a web application.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:env-entry" />
            <xsd:field xpath="javaee:env-entry-name" />
        </xsd:unique>
        <xsd:key name="web-app-role-name-key">
            <xsd:annotation>
                <xsd:documentation>
                    A role-name-key is specified to allow the references
                    from the security-role-refs.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector xpath="javaee:security-role" />
            <xsd:field xpath="javaee:role-name" />
        </xsd:key>
        <xsd:keyref name="web-app-role-name-references"
            refer="javaee:web-app-role-name-key">
            <xsd:annotation>
                <xsd:documentation>
                    The keyref indicates the references from
                    security-role-ref to a specified role-name.
                </xsd:documentation>
            </xsd:annotation>
            <xsd:selector
                xpath="javaee:servlet/javaee:security-role-ref" />
            <xsd:field xpath="javaee:role-link" />
        </xsd:keyref>
    </xsd:element>
    <!-- **************************************************** -->
    <xsd:complexType name="auth-constraintType">
        <xsd:annotation>
            <xsd:documentation>
                The auth-constraintType indicates the user roles that
                should be permitted access to this resource collection.
                The role-name used here must either correspond to the
                role-name of one of the security-role elements defined
                for this web application, or be the specially reserved
                role-name "*" that is a compact syntax for indicating
                all roles in the web application. If both "*" and
                rolenames appear, the container interprets this as all
                roles. If no roles are defined, no user is allowed
                access to the portion of the web application described
                by the containing security-constraint. The container
                matches role names case sensitively when determining
                access.
            </xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:element name="description"
                type="javaee:descriptionType" minOccurs="0"
                maxOccurs="unbounded" />
            <xsd:element name="role-name" type="javaee:role-nameType"
                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