<xsd:element name="user-data-constraint"		   type="javaee:user-data-constraintType"		   minOccurs="0"/>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="servlet-mappingType">    <xsd:annotation>      <xsd:documentation>	The servlet-mappingType defines a mapping between a	servlet and a url pattern.	Used in: web-app      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:element name="servlet-name"		   type="javaee:servlet-nameType"/>      <xsd:element name="url-pattern"		   type="javaee:url-patternType"           minOccurs="1" maxOccurs="unbounded"/>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="servlet-nameType">    <xsd:annotation>      <xsd:documentation>	The servlet-name element contains the canonical name of the	servlet. Each servlet name is unique within the web	application.      </xsd:documentation>    </xsd:annotation>    <xsd:simpleContent>      <xsd:extension base="javaee:nonEmptyStringType"/>    </xsd:simpleContent>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="servletType">    <xsd:annotation>      <xsd:documentation>	The servletType is used to declare a servlet.	It contains the declarative data of a	servlet. If a jsp-file is specified and the load-on-startup	element is present, then the JSP should be precompiled and	loaded.	Used in: web-app      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:group ref="javaee:descriptionGroup"/>      <xsd:element name="servlet-name"		   type="javaee:servlet-nameType"/>      <xsd:choice>	<xsd:element name="servlet-class"		     type="javaee:fully-qualified-classType">	  <xsd:annotation>	    <xsd:documentation>	      The servlet-class element contains the fully	      qualified class name of the servlet.	    </xsd:documentation>	  </xsd:annotation>	</xsd:element>	<xsd:element name="jsp-file"		     type="javaee:jsp-fileType"/>      </xsd:choice>      <xsd:element name="init-param"		   type="javaee:param-valueType"		   minOccurs="0" maxOccurs="unbounded"/>      <xsd:element name="load-on-startup"		   type="javaee:load-on-startupType"		   minOccurs="0">	<xsd:annotation>	  <xsd:documentation>	    The load-on-startup element indicates that this	    servlet should be loaded (instantiated and have	    its init() called) on the startup of the web	    application. The optional contents of these	    element must be an integer indicating the order in	    which the servlet should be loaded. If the value	    is a negative integer, or the element is not	    present, the container is free to load the servlet	    whenever it chooses. If the value is a positive	    integer or 0, the container must load and	    initialize the servlet as the application is	    deployed. The container must guarantee that	    servlets marked with lower integers are loaded	    before servlets marked with higher integers. The	    container may choose the order of loading of	    servlets with the same load-on-start-up value.	  </xsd:documentation>	</xsd:annotation>      </xsd:element>      <xsd:element name="run-as"		   type="javaee:run-asType"		   minOccurs="0"/>      <xsd:element name="security-role-ref"		   type="javaee:security-role-refType"		   minOccurs="0" maxOccurs="unbounded"/>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="session-configType">    <xsd:annotation>      <xsd:documentation>	The session-configType defines the session parameters	for this web application.	Used in: web-app      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:element name="session-timeout"		   type="javaee:xsdIntegerType"		   minOccurs="0">	<xsd:annotation>	  <xsd:documentation>	    The session-timeout element defines the default	    session timeout interval for all sessions created	    in this web application. The specified timeout	    must be expressed in a whole number of minutes.	    If the timeout is 0 or less, the container ensures	    the default behaviour of sessions is never to time	    out. If this element is not specified, the container	    must set its default timeout period.	  </xsd:documentation>	</xsd:annotation>      </xsd:element>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="transport-guaranteeType">    <xsd:annotation>      <xsd:documentation>	The transport-guaranteeType specifies that the communication	between client and server should be NONE, INTEGRAL, or	CONFIDENTIAL. NONE means that the application does not	require any transport guarantees. A value of INTEGRAL means	that the application requires that the data sent between the	client and server be sent in such a way that it can't be	changed in transit. CONFIDENTIAL means that the application	requires that the data be transmitted in a fashion that	prevents other entities from observing the contents of the	transmission. In most cases, the presence of the INTEGRAL or	CONFIDENTIAL flag will indicate that the use of SSL is	required.	Used in: user-data-constraint      </xsd:documentation>    </xsd:annotation>    <xsd:simpleContent>      <xsd:restriction base="javaee:string">	<xsd:enumeration value="NONE"/>	<xsd:enumeration value="INTEGRAL"/>	<xsd:enumeration value="CONFIDENTIAL"/>      </xsd:restriction>    </xsd:simpleContent>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="user-data-constraintType">    <xsd:annotation>      <xsd:documentation>	The user-data-constraintType is used to indicate how	data communicated between the client and container should be	protected.	Used in: security-constraint      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:element name="description"		   type="javaee:descriptionType"		   minOccurs="0"		   maxOccurs="unbounded"/>      <xsd:element name="transport-guarantee"		   type="javaee:transport-guaranteeType"/>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="war-pathType">    <xsd:annotation>      <xsd:documentation>	The elements that use this type designate a path starting	with a "/" and interpreted relative to the root of a WAR	file.      </xsd:documentation>    </xsd:annotation>    <xsd:simpleContent>      <xsd:restriction base="javaee:string">	<xsd:pattern value="/.*"/>      </xsd:restriction>    </xsd:simpleContent>  </xsd:complexType><!-- **************************************************** -->  <xsd:simpleType name="web-app-versionType">    <xsd:annotation>      <xsd:documentation>	This type contains the recognized versions of	web-application supported. It is used to designate the	version of the web application.      </xsd:documentation>    </xsd:annotation>    <xsd:restriction base="xsd:token">      <xsd:enumeration value="2.5"/>    </xsd:restriction>  </xsd:simpleType><!-- **************************************************** -->  <xsd:complexType name="web-appType">    <xsd:choice minOccurs="0" maxOccurs="unbounded">      <xsd:group ref="javaee:descriptionGroup"/>      <xsd:element name="distributable"		   type="javaee:emptyType"/>      <xsd:element name="context-param"		   type="javaee:param-valueType">	<xsd:annotation>	  <xsd:documentation>	    The context-param element contains the declaration	    of a web application's servlet context	    initialization parameters.	  </xsd:documentation>	</xsd:annotation>      </xsd:element>      <xsd:element name="filter"		   type="javaee:filterType"/>      <xsd:element name="filter-mapping"		   type="javaee:filter-mappingType"/>      <xsd:element name="listener"		   type="javaee:listenerType"/>      <xsd:element name="servlet"		   type="javaee:servletType"/>      <xsd:element name="servlet-mapping"		   type="javaee:servlet-mappingType"/>      <xsd:element name="session-config"		   type="javaee:session-configType"/>      <xsd:element name="mime-mapping"		   type="javaee:mime-mappingType"/>      <xsd:element name="welcome-file-list"		   type="javaee:welcome-file-listType"/>      <xsd:element name="error-page"		   type="javaee:error-pageType"/>      <xsd:element name="jsp-config"		   type="javaee:jsp-configType"/>      <xsd:element name="security-constraint"		   type="javaee:security-constraintType"/>      <xsd:element name="login-config"		   type="javaee:login-configType"/>      <xsd:element name="security-role"		   type="javaee:security-roleType"/>      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>      <xsd:element name="message-destination"		   type="javaee:message-destinationType"/>      <xsd:element name="locale-encoding-mapping-list"		   type="javaee:locale-encoding-mapping-listType"/>    </xsd:choice>    <xsd:attribute name="version"		   type="javaee:web-app-versionType"		   use="required"/>    <xsd:attribute name="id" type="xsd:ID"/>    <xsd:attribute name="metadata-complete" type="xsd:boolean">      <xsd:annotation>	<xsd:documentation>	  The metadata-complete attribute defines whether this	  deployment descriptor and other related deployment	  descriptors for this module (e.g., web service	  descriptors) are complete, or whether the class	  files available to this module and packaged with	  this application should be examined for annotations	  that specify deployment information.	  If metadata-complete is set to "true", the deployment	  tool must ignore any annotations that specify deployment	  information, which might be present in the class files	  of the application.	  If metadata-complete is not specified or is set to	  "false", the deployment tool must examine the class	  files of the application for annotations, as	  specified by the specifications.	</xsd:documentation>      </xsd:annotation>    </xsd:attribute>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="web-resource-collectionType">    <xsd:annotation>      <xsd:documentation>	The web-resource-collectionType is used to identify a subset	of the resources and HTTP methods on those resources within	a web application to which a security constraint applies. If	no HTTP methods are specified, then the security constraint	applies to all HTTP methods.	Used in: security-constraint      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:element name="web-resource-name"		   type="javaee:string">	<xsd:annotation>	  <xsd:documentation>	    The web-resource-name contains the name of this web	    resource collection.	  </xsd:documentation>	</xsd:annotation>      </xsd:element>      <xsd:element name="description"		   type="javaee:descriptionType"		   minOccurs="0"		   maxOccurs="unbounded"/>      <xsd:element name="url-pattern"		   type="javaee:url-patternType"		   maxOccurs="unbounded"/>      <xsd:element name="http-method"		   type="javaee:http-methodType"		   minOccurs="0" maxOccurs="unbounded"/>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType><!-- **************************************************** -->  <xsd:complexType name="welcome-file-listType">    <xsd:annotation>      <xsd:documentation>	The welcome-file-list contains an ordered list of welcome	files elements.	Used in: web-app      </xsd:documentation>    </xsd:annotation>    <xsd:sequence>      <xsd:element name="welcome-file"		   type="xsd:string"		   maxOccurs="unbounded">	<xsd:annotation>	  <xsd:documentation>	    The welcome-file element contains file name to use	    as a default welcome file, such as index.html	  </xsd:documentation>	</xsd:annotation>      </xsd:element>    </xsd:sequence>    <xsd:attribute name="id" type="xsd:ID"/>  </xsd:complexType></xsd:schema>