Attachment 155391 Details for Bug 262038 – The approved xsds and an updated plugin.xml

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] The approved xsds and an updated plugin.xml

bug262038.patch (text/plain), 429.74 KB, created by Carl Anderson

on 2010-01-06 00:16:45 EST

(hide)

Description:

Filename:

MIME Type:

Creator: Carl Anderson

Created: 2010-01-06 00:16:45 EST

Size: 429.74 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P org.eclipse.jst.standard.schemas
>Index: plugin.xml
>===================================================================
>RCS file: /cvsroot/webtools/sourceediting/plugins/org.eclipse.jst.standard.schemas/plugin.xml,v
>retrieving revision 1.7
>diff -u -r1.7 plugin.xml
>--- plugin.xml	2 Jun 2008 19:52:19 -0000	1.7
>+++ plugin.xml	6 Jan 2010 05:18:16 -0000
>@@ -26,6 +26,9 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/application_5.xsd"
>                 uri="dtdsAndSchemas/application_5.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/application_6.xsd"
>+                uri="dtdsAndSchemas/application_6.xsd" />
> 
> 
>             <public
>@@ -42,6 +45,9 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/application-client_5.xsd"
>                 uri="dtdsAndSchemas/application-client_5.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/application-client_6.xsd"
>+                uri="dtdsAndSchemas/application-client_6.xsd" />
> 
> 
>             <public
>@@ -51,6 +57,9 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
>                 uri="dtdsAndSchemas/connector_1_5.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd"
>+                uri="dtdsAndSchemas/connector_1_6.xsd" />
> 
> 
>             <public
>@@ -67,6 +76,9 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>                 uri="dtdsAndSchemas/ejb-jar_3_0.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
>+                uri="dtdsAndSchemas/ejb-jar_3_1.xsd" />
> 
> 
>             <uri
>@@ -98,14 +110,23 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/javaee_5.xsd"
>                 uri="dtdsAndSchemas/javaee_5.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/javaee_6.xsd"
>+                uri="dtdsAndSchemas/javaee_6.xsd" />
> 
> 
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd"
>                 uri="dtdsAndSchemas/javaee_web_services_1_2.xsd" />
>             <uri
>+                name="http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.xsd"
>+                uri="dtdsAndSchemas/javaee_web_services_1_3.xsd" />
>+            <uri
>                 name="http://java.sun.com/xml/ns/javaee/javaee_web_services_client_1_2.xsd"
>                 uri="dtdsAndSchemas/javaee_web_services_client_1_2.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/javaee_web_services_client_1_3.xsd"
>+                uri="dtdsAndSchemas/javaee_web_services_client_1_3.xsd" />
> 
>             <uri
>                 name="http://java.sun.com/xml/ns/j2ee/jsp_2_0.xsd"
>@@ -113,6 +134,9 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/j2ee/jsp_2_1.xsd"
>                 uri="dtdsAndSchemas/jsp_2_1.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/j2ee/jsp_2_2.xsd"
>+                uri="dtdsAndSchemas/jsp_2_2.xsd" />
> 
> 
>             <public
>@@ -132,6 +156,15 @@
>             <uri
>                 name="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
>                 uri="dtdsAndSchemas/web-app_2_5.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
>+                uri="dtdsAndSchemas/web-app_3_0.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/web-common_3_0.xsd"
>+                uri="dtdsAndSchemas/web-common_3_0.xsd" />
>+            <uri
>+                name="http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd"
>+                uri="dtdsAndSchemas/web-fragment_3_0.xsd" />
> 
> 
>             <public
>Index: dtdsAndSchemas/ejb-jar_3_1.xsd
>===================================================================
>RCS file: dtdsAndSchemas/ejb-jar_3_1.xsd
>diff -N dtdsAndSchemas/ejb-jar_3_1.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/ejb-jar_3_1.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,3247 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="3.1">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the EJB 3.1 deployment descriptor.
>+      
>+      All EJB deployment descriptors must indicate
>+      the 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:
>+      
>+      <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>+      	  http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
>+      version="3.1">
>+      ...
>+      </ejb-jar>
>+      
>+      The instance documents may indicate the published version of
>+      the schema using the xsi:schemaLocation attribute for the
>+      Java EE namespace with the following location:
>+      
>+      http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="ejb-jar"
>+               type="javaee:ejb-jarType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This is the root of the ejb-jar deployment descriptor.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:key name="ejb-name-key">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The ejb-name element contains the name of an enterprise
>+          bean. The name must be unique within the ejb-jar or
>+          .war file.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:enterprise-beans/*"/>
>+      <xsd:field xpath="javaee:ejb-name"/>
>+    </xsd:key>
>+    <xsd:keyref name="ejb-name-references"
>+                refer="javaee:ejb-name-key">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The keyref indicates the references from
>+          relationship-role-source must be to a specific ejb-name
>+          defined within the scope of enterprise-beans element. 
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath=".//javaee:ejb-relationship-role/javaee:relationship-role-source"/>
>+      <xsd:field xpath="javaee:ejb-name"/>
>+    </xsd:keyref>
>+    <xsd:key name="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:assembly-descriptor/javaee:security-role"/>
>+      <xsd:field xpath="javaee:role-name"/>
>+    </xsd:key>
>+    <xsd:keyref name="role-name-references"
>+                refer="javaee: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:enterprise-beans/*/javaee:security-role-ref"/>
>+      <xsd:field xpath="javaee:role-link"/>
>+    </xsd:keyref>
>+  </xsd:element>
>+
>+
>+
>+
>+  <xsd:complexType name="access-timeoutType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The access-timeoutType represents the maximum amount of
>+        time (in a given time unit) that the container should wait for
>+        a concurrency lock before throwing a timeout exception to the
>+        client.
>+        
>+        A timeout value of 0 means concurrent access is not permitted.
>+        
>+        A timeout value of -1 means wait indefinitely to acquire a lock.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="timeout"
>+                   type="javaee:xsdIntegerType"/>
>+      <xsd:element name="unit"
>+                   type="javaee:time-unit-typeType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="async-methodType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The async-methodType element specifies that a session
>+        bean method has asynchronous invocation semantics.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="method-name"
>+                   type="javaee:string"/>
>+      <xsd:element name="method-params"
>+                   type="javaee:method-paramsType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="activation-configType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The activation-configType defines information about the
>+        expected configuration properties of the message-driven bean
>+        in its operational environment. This may include information
>+        about message acknowledgement, message selector, expected
>+        destination type, etc.
>+        
>+        The configuration information is expressed in terms of
>+        name/value configuration properties.
>+        
>+        The properties that are recognized for a particular
>+        message-driven bean are determined by the messaging type.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="activation-config-property"
>+                   type="javaee:activation-config-propertyType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="activation-config-propertyType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The activation-config-propertyType contains a name/value
>+        configuration property pair for a message-driven bean.
>+        
>+        The properties that are recognized for a particular
>+        message-driven bean are determined by the messaging type.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="activation-config-property-name"
>+                   type="javaee:xsdStringType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The activation-config-property-name element contains
>+            the name for an activation configuration property of
>+            a message-driven bean.
>+            
>+            For JMS message-driven beans, the following property
>+            names are recognized: acknowledgeMode,
>+            messageSelector, destinationType, subscriptionDurability
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="activation-config-property-value"
>+                   type="javaee:xsdStringType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The activation-config-property-value element
>+            contains the value for an activation configuration
>+            property of a message-driven bean.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="around-invokeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The around-invoke type specifies a method on a
>+        class to be called during the around invoke portion of an 
>+        ejb invocation.  Note that each class may have only one
>+        around invoke method and that the method may not be
>+        overloaded.
>+        
>+        If the class element is missing then
>+        the class defining the callback is assumed to be the
>+        interceptor class or component class in scope at the
>+        location in the descriptor in which the around invoke
>+        definition appears.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="class"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"/>
>+      <xsd:element name="method-name"
>+                   type="javaee:java-identifierType"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="around-timeoutType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The around-timeout type specifies a method on a
>+        class to be called during the around-timeout portion of
>+        a timer timeout callback.  Note that each class may have 
>+        only one around-timeout method and that the method may not 
>+        be overloaded.
>+        
>+        If the class element is missing then
>+        the class defining the callback is assumed to be the
>+        interceptor class or component class in scope at the
>+        location in the descriptor in which the around-timeout
>+        definition appears.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="class"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"/>
>+      <xsd:element name="method-name"
>+                   type="javaee:java-identifierType"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="assembly-descriptorType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The assembly-descriptorType defines
>+        application-assembly information.
>+        
>+        The application-assembly information consists of the
>+        following parts: the definition of security roles, the
>+        definition of method permissions, the definition of
>+        transaction attributes for enterprise beans with
>+        container-managed transaction demarcation, the definition
>+        of interceptor bindings, a list of
>+        methods to be excluded from being invoked, and a list of
>+        exception types that should be treated as application exceptions.
>+        
>+        All the parts are optional in the sense that they are
>+        omitted if the lists represented by them are empty.
>+        
>+        Providing an assembly-descriptor in the deployment
>+        descriptor is optional for the ejb-jar or .war file producer.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="security-role"
>+                   type="javaee:security-roleType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="method-permission"
>+                   type="javaee:method-permissionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="container-transaction"
>+                   type="javaee:container-transactionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="interceptor-binding"
>+                   type="javaee:interceptor-bindingType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination"
>+                   type="javaee:message-destinationType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="exclude-list"
>+                   type="javaee:exclude-listType"
>+                   minOccurs="0"/>
>+      <xsd:element name="application-exception"
>+                   type="javaee:application-exceptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cmp-fieldType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The cmp-fieldType describes a container-managed field. The
>+        cmp-fieldType contains an optional description of the field,
>+        and the name of the field.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="field-name"
>+                   type="javaee:java-identifierType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The field-name element specifies the name of a
>+            container managed field.
>+            
>+            The name of the cmp-field of an entity bean with
>+            cmp-version 2.x must begin with a lowercase
>+            letter. This field is accessed by methods whose
>+            names consists of the name of the field specified by
>+            field-name in which the first letter is uppercased,
>+            prefixed by "get" or "set".
>+            
>+            The name of the cmp-field of an entity bean with
>+            cmp-version 1.x must denote a public field of the
>+            enterprise bean class or one of its superclasses.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cmp-versionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The cmp-versionType specifies the version of an entity bean
>+        with container-managed persistence. It is used by
>+        cmp-version elements.
>+        
>+        The value must be one of the two following:
>+        
>+        1.x
>+        2.x
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="1.x"/>
>+        <xsd:enumeration value="2.x"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cmr-fieldType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The cmr-fieldType describes the bean provider's view of
>+        a relationship. It consists of an optional description, and
>+        the name and the class type of a field in the source of a
>+        role of a relationship. The cmr-field-name element
>+        corresponds to the name used for the get and set accessor
>+        methods for the relationship. The cmr-field-type element is
>+        used only for collection-valued cmr-fields. It specifies the
>+        type of the collection that is used.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="cmr-field-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The cmr-field-name element specifies the name of a
>+            logical relationship field in the entity bean
>+            class. The name of the cmr-field must begin with a
>+            lowercase letter. This field is accessed by methods
>+            whose names consist of the name of the field
>+            specified by cmr-field-name in which the first
>+            letter is uppercased, prefixed by "get" or "set".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="cmr-field-type"
>+                   type="javaee:cmr-field-typeType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cmr-field-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The cmr-field-type element specifies the class of a
>+        collection-valued logical relationship field in the entity
>+        bean class. The value of an element using cmr-field-typeType
>+        must be either: java.util.Collection or java.util.Set.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="java.util.Collection"/>
>+        <xsd:enumeration value="java.util.Set"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="concurrency-management-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The concurrency-management-typeType specifies the way concurrency
>+        is managed for a singleton or stateful session bean.  
>+        
>+        The concurrency management type must be one of the following:
>+        
>+        Bean
>+        Container
>+        
>+        Bean managed concurrency can only be specified for a singleton bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Bean"/>
>+        <xsd:enumeration value="Container"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="concurrent-lock-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The concurrent-lock-typeType specifies how the container must
>+        manage concurrent access to a method of a Singleton bean 
>+        with container-managed concurrency.
>+        
>+        The container managed concurrency lock type must be one 
>+        of the following :
>+        
>+        Read
>+        Write
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Read"/>
>+        <xsd:enumeration value="Write"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="concurrent-methodType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The concurrent-methodType specifies information about a method
>+        of a bean with container managed concurrency.
>+        
>+        The optional lock element specifies the kind of concurrency 
>+        lock asssociated with the method.
>+        
>+        The optional access-timeout element specifies the amount of
>+        time (in a given time unit) the container should wait for a
>+        concurrency lock before throwing an exception to the client.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="method"
>+                   type="javaee:named-methodType"/>
>+      <xsd:element name="lock"
>+                   type="javaee:concurrent-lock-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="access-timeout"
>+                   type="javaee:access-timeoutType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="container-transactionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The container-transactionType specifies how the container
>+        must manage transaction scopes for the enterprise bean's
>+        method invocations. It defines an optional description, a
>+        list of method elements, and a transaction attribute. The
>+        transaction attribute is to be applied to all the specified
>+        methods.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="method"
>+                   type="javaee:methodType"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="trans-attribute"
>+                   type="javaee:trans-attributeType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="depends-onType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The depends-onType is used to express initialization 
>+        ordering dependencies between Singleton components.
>+        The depends-onType specifies the names of one or more
>+        Singleton beans in the same application as the referring
>+        Singleton, each of which must be initialized before
>+        the referring bean.  
>+        
>+        Each dependent bean is expressed using ejb-link syntax.
>+        The order in which dependent beans are initialized at 
>+        runtime is not guaranteed to match the order in which
>+        they are listed.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-linkType"
>+                   minOccurs="1"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-classType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The ejb-classType contains the fully-qualified name of the
>+        enterprise bean's class. It is used by ejb-class elements. 
>+        
>+        Example:
>+        
>+        <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-jarType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The ejb-jarType defines the root element of the EJB
>+        deployment descriptor. It contains
>+        
>+        - an optional description of the ejb-jar file
>+        - an optional display name
>+        - an optional icon that contains a small and a large
>+        icon file name
>+        - an optional module name. Only applicable to
>+        stand-alone ejb-jars or ejb-jars packaged in an ear.
>+        Ignored if specified for an ejb-jar.xml within a .war.
>+        In that case, standard .war module-name rules apply.
>+        - structural information about all included
>+        enterprise beans that is not specified through
>+        annotations
>+        - structural information about interceptor classes
>+        - a descriptor for container managed relationships, 
>+        if any. 
>+        - an optional application-assembly descriptor
>+        - an optional name of an ejb-client-jar file for the 
>+        ejb-jar.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="module-name"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="enterprise-beans"
>+                   type="javaee:enterprise-beansType"
>+                   minOccurs="0"/>
>+      <xsd:element name="interceptors"
>+                   type="javaee:interceptorsType"
>+                   minOccurs="0"/>
>+      <xsd:element name="relationships"
>+                   type="javaee:relationshipsType"
>+                   minOccurs="0">
>+        <xsd:unique name="relationship-name-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The ejb-relation-name contains the name of a
>+              relation. The name must be unique within
>+              relationships.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:ejb-relation"/>
>+          <xsd:field xpath="javaee:ejb-relation-name"/>
>+        </xsd:unique>
>+      </xsd:element>
>+      <xsd:element name="assembly-descriptor"
>+                   type="javaee:assembly-descriptorType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Providing an assembly-descriptor in the deployment
>+            descriptor is optional for the ejb-jar or .war file
>+            producer.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="ejb-client-jar"
>+                   type="javaee:pathType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The optional ejb-client-jar element specifies a JAR
>+            file that contains the class files necessary for a
>+            client program to access the
>+            enterprise beans in the ejb-jar file.
>+            
>+            Example:
>+            
>+            	  <ejb-client-jar>employee_service_client.jar
>+            	  </ejb-client-jar>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="version"
>+                   type="javaee:dewey-versionType"
>+                   fixed="3.1"
>+                   use="required">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The version specifies the version of the
>+          EJB specification that the instance document must 
>+          comply with. This information enables deployment tools
>+          to validate a particular EJB Deployment
>+          Descriptor with respect to a specific version of the EJB
>+          schema. 
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <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:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The ejb-nameType specifies an enterprise bean's name. It is
>+        used by ejb-name elements. This name is assigned by the
>+        file producer to name the enterprise bean in the
>+        ejb-jar or .war file's deployment descriptor. The name must be
>+        unique among the names of the enterprise beans in the same
>+        ejb-jar or .war file.
>+        
>+        There is no architected relationship between the used
>+        ejb-name in the deployment descriptor and the JNDI name that
>+        the Deployer will assign to the enterprise bean's home.
>+        
>+        The name for an entity bean must conform to the lexical
>+        rules for an NMTOKEN.
>+        
>+        Example:
>+        
>+        <ejb-name>EmployeeService</ejb-name>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:xsdNMTOKENType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-relationType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The ejb-relationType describes a relationship between two
>+        entity beans with container-managed persistence.  It is used
>+        by ejb-relation elements. It contains a description; an
>+        optional ejb-relation-name element; and exactly two
>+        relationship role declarations, defined by the
>+        ejb-relationship-role elements. The name of the
>+        relationship, if specified, is unique within the ejb-jar
>+        file.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-relation-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The ejb-relation-name element provides a unique name
>+            within the ejb-jar file for a relationship.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="ejb-relationship-role"
>+                   type="javaee:ejb-relationship-roleType"/>
>+      <xsd:element name="ejb-relationship-role"
>+                   type="javaee:ejb-relationship-roleType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-relationship-roleType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The ejb-relationship-roleType describes a role within a
>+        relationship. There are two roles in each relationship.
>+        
>+        The ejb-relationship-roleType contains an optional
>+        description; an optional name for the relationship role; a
>+        specification of the multiplicity of the role; an optional
>+        specification of cascade-delete functionality for the role;
>+        the role source; and a declaration of the cmr-field, if any,
>+        by means of which the other side of the relationship is
>+        accessed from the perspective of the role source.
>+        
>+        The multiplicity and role-source element are mandatory.
>+        
>+        The relationship-role-source element designates an entity
>+        bean by means of an ejb-name element. For bidirectional
>+        relationships, both roles of a relationship must declare a
>+        relationship-role-source element that specifies a cmr-field
>+        in terms of which the relationship is accessed. The lack of
>+        a cmr-field element in an ejb-relationship-role specifies
>+        that the relationship is unidirectional in navigability and
>+        the entity bean that participates in the relationship is
>+        "not aware" of the relationship.
>+        
>+        Example:
>+        
>+        <ejb-relation>
>+        <ejb-relation-name>Product-LineItem</ejb-relation-name>
>+        <ejb-relationship-role>
>+        	  <ejb-relationship-role-name>product-has-lineitems
>+        	  </ejb-relationship-role-name>
>+        	  <multiplicity>One</multiplicity>
>+        	  <relationship-role-source>
>+        	  <ejb-name>ProductEJB</ejb-name>
>+        	  </relationship-role-source>
>+        </ejb-relationship-role>
>+        </ejb-relation>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-relationship-role-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The ejb-relationship-role-name element defines a
>+            name for a role that is unique within an
>+            ejb-relation. Different relationships can use the
>+            same name for a role.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="multiplicity"
>+                   type="javaee:multiplicityType"/>
>+      <xsd:element name="cascade-delete"
>+                   type="javaee:emptyType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The cascade-delete element specifies that, within a
>+            particular relationship, the lifetime of one or more
>+            entity beans is dependent upon the lifetime of
>+            another entity bean. The cascade-delete element can
>+            only be specified for an ejb-relationship-role
>+            element contained in an ejb-relation element in
>+            which the other ejb-relationship-role
>+            element specifies a multiplicity of One.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="relationship-role-source"
>+                   type="javaee:relationship-role-sourceType"/>
>+      <xsd:element name="cmr-field"
>+                   type="javaee:cmr-fieldType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="enterprise-beansType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The enterprise-beansType declares one or more enterprise
>+        beans. Each bean can be a session, entity or message-driven
>+        bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:choice maxOccurs="unbounded">
>+      <xsd:element name="session"
>+                   type="javaee:session-beanType">
>+        <xsd:unique name="session-ejb-local-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 component's environment and is relative to the
>+              java:comp/env context.  The name must be unique within
>+              the component.
>+              
>+              It is recommended that name be 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="session-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
>+              component's environment and is relative to the
>+              java:comp/env context. The name must be unique
>+              within the component.
>+              
>+              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="session-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 component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-env-ref"/>
>+          <xsd:field xpath="javaee:resource-env-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="session-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 message destination reference name used in the component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:message-destination-ref"/>
>+          <xsd:field xpath="javaee:message-destination-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="session-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 an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-ref"/>
>+          <xsd:field xpath="javaee:res-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="session-env-entry-name-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The env-entry-name element contains the name of a
>+              component's environment entry.  The name is a JNDI
>+              name relative to the java:comp/env context.  The
>+              name must be unique within an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:env-entry"/>
>+          <xsd:field xpath="javaee:env-entry-name"/>
>+        </xsd:unique>
>+      </xsd:element>
>+      <xsd:element name="entity"
>+                   type="javaee:entity-beanType">
>+        <xsd:unique name="entity-ejb-local-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 component's environment and is relative to the
>+              java:comp/env context.  The name must be unique within
>+              the component.
>+              
>+              It is recommended that name be 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="entity-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
>+              component's environment and is relative to the
>+              java:comp/env context. The name must be unique
>+              within the component.
>+              
>+              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="entity-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 component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-env-ref"/>
>+          <xsd:field xpath="javaee:resource-env-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="entity-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 message destination reference name used in the component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:message-destination-ref"/>
>+          <xsd:field xpath="javaee:message-destination-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="entity-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 an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-ref"/>
>+          <xsd:field xpath="javaee:res-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="entity-env-entry-name-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The env-entry-name element contains the name of a
>+              component's environment entry.  The name is a JNDI
>+              name relative to the java:comp/env context.  The
>+              name must be unique within an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:env-entry"/>
>+          <xsd:field xpath="javaee:env-entry-name"/>
>+        </xsd:unique>
>+      </xsd:element>
>+      <xsd:element name="message-driven"
>+                   type="javaee:message-driven-beanType">
>+        <xsd:unique name="messaged-ejb-local-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 component's environment and is relative to the
>+              java:comp/env context.  The name must be unique within
>+              the component.
>+              
>+              It is recommended that name be 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="messaged-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
>+              component's environment and is relative to the
>+              java:comp/env context. The name must be unique
>+              within the component.
>+              
>+              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="messaged-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 component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-env-ref"/>
>+          <xsd:field xpath="javaee:resource-env-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="messaged-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 message destination reference name used in the component
>+              code. The name is a JNDI name relative to the
>+              java:comp/env context and must be unique within an
>+              component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:message-destination-ref"/>
>+          <xsd:field xpath="javaee:message-destination-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="messaged-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 an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:resource-ref"/>
>+          <xsd:field xpath="javaee:res-ref-name"/>
>+        </xsd:unique>
>+        <xsd:unique name="messaged-env-entry-name-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The env-entry-name element contains the name of a
>+              component's environment entry.  The name is a JNDI
>+              name relative to the java:comp/env context.  The
>+              name must be unique within an component.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:env-entry"/>
>+          <xsd:field xpath="javaee:env-entry-name"/>
>+        </xsd:unique>
>+      </xsd:element>
>+    </xsd:choice>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="entity-beanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The entity-beanType declares an entity bean. The declaration
>+        consists of:
>+        
>+        - an optional description
>+        - an optional display name
>+        - an optional icon element that contains a small and a large 
>+        icon file name
>+        - a unique name assigned to the enterprise bean
>+        in the deployment descriptor
>+        - an optional mapped-name element that can be used to provide
>+        vendor-specific deployment information such as the physical
>+        jndi-name of the entity bean's remote home interface. This 
>+        element is not required to be supported by all implementations.
>+        Any use of this element is non-portable.
>+        - the names of the entity bean's remote home 
>+        and remote interfaces, if any
>+        - the names of the entity bean's local home and local
>+        interfaces, if any
>+        - the entity bean's implementation class
>+        - the optional entity bean's persistence management type. If 
>+        this element is not specified it is defaulted to Container.
>+        - the entity bean's primary key class name
>+        - an indication of the entity bean's reentrancy
>+        - an optional specification of the 
>+        entity bean's cmp-version
>+        - an optional specification of the entity bean's
>+        abstract schema name
>+        - an optional list of container-managed fields
>+        - an optional specification of the primary key 
>+        field
>+        - an optional declaration of the bean's environment 
>+        entries
>+        - an optional declaration of the bean's EJB 
>+        references
>+        - an optional declaration of the bean's local 
>+        EJB references
>+        - an optional declaration of the bean's web 
>+        service references
>+        - an optional declaration of the security role 
>+        references
>+        - an optional declaration of the security identity
>+        to be used for the execution of the bean's methods
>+        - an optional declaration of the bean's 
>+        resource manager connection factory references
>+        - an optional declaration of the bean's
>+        resource environment references
>+        - an optional declaration of the bean's message 
>+        destination references
>+        - an optional set of query declarations
>+        for finder and select methods for an entity
>+        bean with cmp-version 2.x.
>+        
>+        The optional abstract-schema-name element must be specified
>+        for an entity bean with container-managed persistence and
>+        cmp-version 2.x.
>+        
>+        The optional primkey-field may be present in the descriptor
>+        if the entity's persistence-type is Container.
>+        
>+        The optional cmp-version element may be present in the
>+        descriptor if the entity's persistence-type is Container. If
>+        the persistence-type is Container and the cmp-version
>+        element is not specified, its value defaults to 2.x.
>+        
>+        The optional home and remote elements must be specified if
>+        the entity bean cmp-version is 1.x.
>+        
>+        The optional home and remote elements must be specified if
>+        the entity bean has a remote home and remote interface.
>+        
>+        The optional local-home and local elements must be specified
>+        if the entity bean has a local home and local interface.
>+        
>+        Either both the local-home and the local elements or both
>+        the home and the remote elements must be specified.
>+        
>+        The optional query elements must be present if the
>+        persistence-type is Container and the cmp-version is 2.x and
>+        query methods other than findByPrimaryKey have been defined
>+        for the entity bean.
>+        
>+        The other elements that are optional are "optional" in the
>+        sense that they are omitted if the lists represented by them
>+        are empty.
>+        
>+        At least one cmp-field element must be present in the
>+        descriptor if the entity's persistence-type is Container and
>+        the cmp-version is 1.x, and none must not be present if the
>+        entity's persistence-type is Bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-nameType"/>
>+      <xsd:element name="mapped-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0"/>
>+      <xsd:element name="home"
>+                   type="javaee:homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="remote"
>+                   type="javaee:remoteType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local-home"
>+                   type="javaee:local-homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local"
>+                   type="javaee:localType"
>+                   minOccurs="0"/>
>+      <xsd:element name="ejb-class"
>+                   type="javaee:ejb-classType"/>
>+      <xsd:element name="persistence-type"
>+                   type="javaee:persistence-typeType"/>
>+      <xsd:element name="prim-key-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The prim-key-class element contains the
>+            fully-qualified name of an
>+            entity bean's primary key class.
>+            
>+            If the definition of the primary key class is
>+            deferred to deployment time, the prim-key-class 
>+            element should specify java.lang.Object.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="reentrant"
>+                   type="javaee:true-falseType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The reentrant element specifies whether an entity
>+            bean is reentrant or not.
>+            
>+            The reentrant element must be one of the two
>+            following: true or false
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="cmp-version"
>+                   type="javaee:cmp-versionType"
>+                   minOccurs="0"/>
>+      <xsd:element name="abstract-schema-name"
>+                   type="javaee:java-identifierType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The abstract-schema-name element specifies the name
>+            of the abstract schema type of an entity bean with 
>+            cmp-version 2.x. It is used in EJB QL queries. 
>+            
>+            For example, the abstract-schema-name for an entity 
>+            bean whose local interface is 
>+            com.acme.commerce.Order might be Order. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="cmp-field"
>+                   type="javaee:cmp-fieldType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="primkey-field"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The primkey-field element is used to specify the
>+            name of the primary key field for an entity with
>+            container-managed persistence.
>+            
>+            The primkey-field must be one of the fields declared
>+            in the cmp-field element, and the type of the field
>+            must be the same as the primary key type.
>+            
>+            The primkey-field element is not used if the primary
>+            key maps to multiple container-managed fields
>+            (i.e. the key is a compound key). In this case, the
>+            fields of the primary key class must be public, and
>+            their names must correspond to the field names of
>+            the entity bean class that comprise the key.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>+      <xsd:element name="security-role-ref"
>+                   type="javaee:security-role-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="security-identity"
>+                   type="javaee:security-identityType"
>+                   minOccurs="0"/>
>+      <xsd:element name="query"
>+                   type="javaee:queryType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="exclude-listType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The exclude-listType specifies one or more methods which
>+        the Assembler marks to be uncallable.
>+        
>+        If the method permission relation contains methods that are
>+        in the exclude list, the Deployer should consider those
>+        methods to be uncallable.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="method"
>+                   type="javaee:methodType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="application-exceptionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The application-exceptionType declares an application
>+        exception. The declaration consists of:
>+        
>+        - the exception class. When the container receives
>+        an exception of this type, it is required to 
>+        forward this exception as an applcation exception 
>+        to the client regardless of whether it is a checked
>+        or unchecked exception.
>+        - an optional rollback element. If this element is 
>+        set to true, the container must rollback the current 
>+        transaction before forwarding the exception to the
>+        client.  If not specified, it defaults to false.
>+        - an optional inherited element. If this element is 
>+        set to true, subclasses of the exception class type
>+        are also automatically considered application 
>+        exceptions (unless overriden at a lower level).
>+        If set to false, only the exception class type is
>+        considered an application-exception, not its
>+        exception subclasses. If not specified, this
>+        value defaults to true.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="exception-class"
>+                   type="javaee:fully-qualified-classType"/>
>+      <xsd:element name="rollback"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="inherited"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="interceptorsType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The interceptorsType element declares one or more interceptor
>+        classes used by components within this ejb-jar or .war.  The declaration
>+        consists of :
>+        
>+        - An optional description.
>+        - One or more interceptor elements.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="interceptor"
>+                   type="javaee:interceptorType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="interceptorType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The interceptorType element declares information about a single
>+        interceptor class.  It consists of :
>+        
>+        - An optional description.
>+        - The fully-qualified name of the interceptor class.
>+        - An optional list of around invoke methods declared on the
>+        interceptor class and/or its super-classes.
>+        - An optional list of around timeout methods declared on the
>+        interceptor class and/or its super-classes.
>+        - An optional list environment dependencies for the interceptor
>+        class and/or its super-classes.
>+        - An optional list of post-activate methods declared on the
>+        interceptor class and/or its super-classes.
>+        - An optional list of pre-passivate methods declared on the
>+        interceptor class and/or its super-classes.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="interceptor-class"
>+                   type="javaee:fully-qualified-classType"/>
>+      <xsd:element name="around-invoke"
>+                   type="javaee:around-invokeType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="around-timeout"
>+                   type="javaee:around-timeoutType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>+      <xsd:element name="post-activate"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="pre-passivate"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="interceptor-bindingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The interceptor-bindingType element describes the binding of
>+        interceptor classes to beans within the ejb-jar or .war.
>+        It consists of :
>+        
>+        - An optional description.
>+        - The name of an ejb within the module or the wildcard value "*",
>+        which is used to define interceptors that are bound to all
>+        beans in the ejb-jar or .war.
>+        - A list of interceptor classes that are bound to the contents of
>+        the ejb-name element or a specification of the total ordering
>+        over the interceptors defined for the given level and above.
>+        - An optional exclude-default-interceptors element.  If set to true,
>+        specifies that default interceptors are not to be applied to 
>+        a bean-class and/or business method.
>+        - An optional exclude-class-interceptors element.  If set to true,
>+        specifies that class interceptors are not to be applied to 
>+        a business method.
>+        - An optional set of method elements for describing the name/params
>+        of a method-level interceptor.
>+        
>+        Interceptors bound to all classes using the wildcard syntax
>+        "*" are default interceptors for the components in the ejb-jar or .war. 
>+        In addition, interceptors may be bound at the level of the bean
>+        class (class-level interceptors) or business methods (method-level
>+        interceptors ).
>+        
>+        The binding of interceptors to classes is additive.  If interceptors
>+        are bound at the class-level and/or default-level as well as the
>+        method-level, both class-level and/or default-level as well as
>+        method-level will apply. 
>+        
>+        There are four possible styles of the interceptor element syntax :
>+        
>+        1.
>+        <interceptor-binding>
>+        <ejb-name>*</ejb-name>
>+        <interceptor-class>INTERCEPTOR</interceptor-class>
>+        </interceptor-binding>
>+        
>+        Specifying the ejb-name as the wildcard value "*" designates
>+        default interceptors (interceptors that apply to all session and
>+        message-driven beans contained in the ejb-jar or .war).
>+        
>+        2. 
>+        <interceptor-binding>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <interceptor-class>INTERCEPTOR</interceptor-class>
>+        </interceptor-binding>
>+        
>+        This style is used to refer to interceptors associated with the
>+        specified enterprise bean(class-level interceptors).
>+        
>+        3. 
>+        <interceptor-binding>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <interceptor-class>INTERCEPTOR</interceptor-class>
>+        <method>
>+        <method-name>METHOD</method-name>
>+        </method>
>+        </interceptor-binding>
>+        
>+        This style is used to associate a method-level interceptor with 
>+        the specified enterprise bean.  If there are multiple methods
>+        with the same overloaded name, the element of this style refers
>+        to all the methods with the overloaded name.  Method-level
>+        interceptors can only be associated with business methods of the
>+        bean class.   Note that the wildcard value "*" cannot be used
>+        to specify method-level interceptors.
>+        
>+        4. 
>+        <interceptor-binding>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <interceptor-class>INTERCEPTOR</interceptor-class>
>+        <method>
>+        <method-name>METHOD</method-name>
>+        <method-params>
>+        <method-param>PARAM-1</method-param>
>+        <method-param>PARAM-2</method-param>
>+        ...
>+        <method-param>PARAM-N</method-param>
>+        </method-params>
>+        </method>
>+        </interceptor-binding>
>+        
>+        This style is used to associate a method-level interceptor with 
>+        the specified method of the specified enterprise bean.  This 
>+        style is used to refer to a single method within a set of methods
>+        with an overloaded name.  The values PARAM-1 through PARAM-N
>+        are the fully-qualified Java types of the method's input parameters
>+        (if the method has no input arguments, the method-params element
>+        contains no method-param elements). Arrays are specified by the
>+        array element's type, followed by one or more pair of square 
>+        brackets (e.g. int[][]).
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:string"/>
>+      <xsd:choice>
>+        <xsd:element name="interceptor-class"
>+                     type="javaee:fully-qualified-classType"
>+                     minOccurs="0"
>+                     maxOccurs="unbounded"/>
>+        <xsd:element name="interceptor-order"
>+                     type="javaee:interceptor-orderType"
>+                     minOccurs="1"/>
>+      </xsd:choice>
>+      <xsd:element name="exclude-default-interceptors"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="exclude-class-interceptors"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="interceptor-orderType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The interceptor-orderType element describes a total ordering
>+        of interceptor classes.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="interceptor-class"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="1"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="named-methodType">
>+    <xsd:sequence>
>+      <xsd:element name="method-name"
>+                   type="javaee:string"/>
>+      <xsd:element name="method-params"
>+                   type="javaee:method-paramsType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="init-methodType">
>+    <xsd:sequence>
>+      <xsd:element name="create-method"
>+                   type="javaee:named-methodType"/>
>+      <xsd:element name="bean-method"
>+                   type="javaee:named-methodType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="remove-methodType">
>+    <xsd:sequence>
>+      <xsd:element name="bean-method"
>+                   type="javaee:named-methodType"/>
>+      <xsd:element name="retain-if-exception"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-driven-beanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The message-driven element declares a message-driven
>+        bean. The declaration consists of:
>+        
>+        - an optional description
>+        - an optional display name
>+        - an optional icon element that contains a small and a large 
>+        icon file name. 
>+        - a name assigned to the enterprise bean in
>+        the deployment descriptor
>+        - an optional mapped-name element that can be used to provide
>+        vendor-specific deployment information such as the physical
>+        jndi-name of destination from which this message-driven bean
>+        should consume.  This element is not required to be supported 
>+        by all implementations.  Any use of this element is non-portable.
>+        - the message-driven bean's implementation class
>+        - an optional declaration of the bean's messaging 
>+        type 
>+        - an optional declaration of the bean's timeout method for
>+        handling programmatically created timers
>+        - an optional declaration of timers to be automatically created at
>+        deployment time
>+        - the optional message-driven bean's transaction management 
>+        type. If it is not defined, it is defaulted to Container.
>+        - an optional declaration of the bean's 
>+        message-destination-type
>+        - an optional declaration of the bean's 
>+        message-destination-link
>+        - an optional declaration of the message-driven bean's
>+        activation configuration properties
>+        - an optional list of the message-driven bean class and/or
>+        superclass around-invoke methods.
>+        - an optional list of the message-driven bean class and/or
>+        superclass around-timeout methods.
>+        - an optional declaration of the bean's environment
>+        entries
>+        - an optional declaration of the bean's EJB references
>+        - an optional declaration of the bean's local EJB
>+        references
>+        - an optional declaration of the bean's web service
>+        references
>+        - an optional declaration of the security role 
>+        references
>+        - an optional declaration of the security
>+        identity to be used for the execution of the bean's
>+        methods
>+        - an optional declaration of the bean's 
>+        resource manager connection factory 
>+        references
>+        - an optional declaration of the bean's resource
>+        environment references.
>+        - an optional declaration of the bean's message 
>+        destination references
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-nameType"/>
>+      <xsd:element name="mapped-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0"/>
>+      <xsd:element name="ejb-class"
>+                   type="javaee:ejb-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The ejb-class element specifies the fully qualified name
>+            of the bean class for this ejb.  It is required unless
>+            there is a component-defining annotation for the same
>+            ejb-name.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="messaging-type"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The messaging-type element specifies the message
>+            listener interface of the message-driven bean. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="timeout-method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The timeout-method element specifies the method that
>+            will receive callbacks for programmatically
>+            created timers.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="timer"
>+                   type="javaee:timerType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="transaction-type"
>+                   type="javaee:transaction-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="message-destination-type"
>+                   type="javaee:message-destination-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="message-destination-link"
>+                   type="javaee:message-destination-linkType"
>+                   minOccurs="0"/>
>+      <xsd:element name="activation-config"
>+                   type="javaee:activation-configType"
>+                   minOccurs="0"/>
>+      <xsd:element name="around-invoke"
>+                   type="javaee:around-invokeType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="around-timeout"
>+                   type="javaee:around-timeoutType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>+      <xsd:element name="security-role-ref"
>+                   type="javaee:security-role-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+      </xsd:element>
>+      <xsd:element name="security-identity"
>+                   type="javaee:security-identityType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="methodType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The methodType is used to denote a method of an enterprise
>+        bean's business, home, component, and/or web service endpoint
>+        interface, or, in the case of a message-driven bean, the
>+        bean's message listener method, or a set of such
>+        methods. The ejb-name element must be the name of one of the
>+        enterprise beans declared in the deployment descriptor; the
>+        optional method-intf element allows to distinguish between a
>+        method with the same signature that is multiply defined
>+        across the business, home, component, and/or web service 
>+        endpoint nterfaces; the method-name element specifies the 
>+        method name; and the optional method-params elements identify 
>+        a single method among multiple methods with an overloaded
>+        method name.
>+        
>+        There are three possible styles of using methodType element
>+        within a method element:
>+        
>+        1.
>+        <method>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <method-name>*</method-name>
>+        </method>
>+        
>+        This style is used to refer to all the methods of the
>+        specified enterprise bean's business, home, component, 
>+        and/or web service endpoint interfaces.
>+        
>+        2.
>+        <method>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <method-name>METHOD</method-name>
>+        </method>
>+        
>+        This style is used to refer to the specified method of
>+        the specified enterprise bean. If there are multiple
>+        methods with the same overloaded name, the element of
>+        this style refers to all the methods with the overloaded
>+        name.
>+        
>+        3.
>+        <method>
>+        <ejb-name>EJBNAME</ejb-name>
>+        <method-name>METHOD</method-name>
>+        <method-params>
>+        	  <method-param>PARAM-1</method-param>
>+        	  <method-param>PARAM-2</method-param>
>+        	  ...
>+        	  <method-param>PARAM-n</method-param>
>+        </method-params>
>+        </method>
>+        
>+        This style is used to refer to a single method within a
>+        set of methods with an overloaded name. PARAM-1 through
>+        PARAM-n are the fully-qualified Java types of the
>+        method's input parameters (if the method has no input
>+        arguments, the method-params element contains no
>+        method-param elements). Arrays are specified by the
>+        array element's type, followed by one or more pair of
>+        square brackets (e.g. int[][]). If there are multiple
>+        methods with the same overloaded name, this style refers
>+        to all of the overloaded methods. 
>+        
>+        Examples:
>+        
>+        Style 1: The following method element refers to all the
>+        methods of the EmployeeService bean's business, home, 
>+        component, and/or web service endpoint interfaces:
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-name>*</method-name>
>+        </method>
>+        
>+        Style 2: The following method element refers to all the
>+        create methods of the EmployeeService bean's home
>+        interface(s).
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-name>create</method-name>
>+        </method>
>+        
>+        Style 3: The following method element refers to the
>+        create(String firstName, String LastName) method of the
>+        EmployeeService bean's home interface(s).
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-name>create</method-name>
>+        <method-params>
>+        	  <method-param>java.lang.String</method-param>
>+        	  <method-param>java.lang.String</method-param>
>+        </method-params>
>+        </method>
>+        
>+        The following example illustrates a Style 3 element with
>+        more complex parameter types. The method 
>+        foobar(char s, int i, int[] iar, mypackage.MyClass mycl, 
>+        mypackage.MyClass[][] myclaar) would be specified as:
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-name>foobar</method-name>
>+        <method-params>
>+        	  <method-param>char</method-param>
>+        	  <method-param>int</method-param>
>+        	  <method-param>int[]</method-param>
>+        	  <method-param>mypackage.MyClass</method-param>
>+        	  <method-param>mypackage.MyClass[][]</method-param>
>+        </method-params>
>+        </method>
>+        
>+        The optional method-intf element can be used when it becomes
>+        necessary to differentiate between a method that is multiply
>+        defined across the enterprise bean's business, home, component,
>+        and/or web service endpoint interfaces with the same name and
>+        signature. However, if the same method is a method of both the
>+        local business interface, and the local component interface, 
>+        the same attribute applies to the method for both interfaces.
>+        Likewise, if the same method is a method of both the remote 
>+        business interface and the remote component interface, the same
>+        attribute applies to the method for both interfaces.
>+        
>+        For example, the method element
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-intf>Remote</method-intf>
>+        <method-name>create</method-name>
>+        <method-params>
>+        	  <method-param>java.lang.String</method-param>
>+        	  <method-param>java.lang.String</method-param>
>+        </method-params>
>+        </method>
>+        
>+        can be used to differentiate the create(String, String)
>+        method defined in the remote interface from the
>+        create(String, String) method defined in the remote home
>+        interface, which would be defined as
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-intf>Home</method-intf>
>+        <method-name>create</method-name>
>+        <method-params>
>+        	  <method-param>java.lang.String</method-param>
>+        	  <method-param>java.lang.String</method-param>
>+        </method-params>
>+        </method>
>+        
>+        and the create method that is defined in the local home
>+        interface which would be defined as
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-intf>LocalHome</method-intf>
>+        <method-name>create</method-name>
>+        <method-params>
>+        	  <method-param>java.lang.String</method-param>
>+        	  <method-param>java.lang.String</method-param>
>+        </method-params>
>+        </method>
>+        
>+        The method-intf element can be used with all three Styles
>+        of the method element usage. For example, the following
>+        method element example could be used to refer to all the
>+        methods of the EmployeeService bean's remote home interface
>+        and the remote business interface.
>+        
>+        <method>
>+        <ejb-name>EmployeeService</ejb-name>
>+        <method-intf>Home</method-intf>
>+        <method-name>*</method-name>
>+        </method>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-nameType"/>
>+      <xsd:element name="method-intf"
>+                   type="javaee:method-intfType"
>+                   minOccurs="0">
>+      </xsd:element>
>+      <xsd:element name="method-name"
>+                   type="javaee:method-nameType"/>
>+      <xsd:element name="method-params"
>+                   type="javaee:method-paramsType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="method-intfType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The method-intf element allows a method element to
>+        differentiate between the methods with the same name and
>+        signature that are multiply defined across the home and
>+        component interfaces (e.g, in both an enterprise bean's
>+        remote and local interfaces or in both an enterprise bean's
>+        home and remote interfaces, etc.); the component and web
>+        service endpoint interfaces, and so on. 
>+        
>+        Local applies to the local component interface, local business 
>+        interfaces, and the no-interface view. 
>+        
>+        Remote applies to both remote component interface and the remote 
>+        business interfaces.  
>+        
>+        ServiceEndpoint refers to methods exposed through a web service
>+        endpoint.
>+        
>+        Timer refers to the bean's timeout callback methods.
>+        
>+        MessageEndpoint refers to the methods of a message-driven bean's
>+        message-listener interface.
>+        
>+        The method-intf element must be one of the following:
>+        
>+        Home
>+        Remote
>+        LocalHome
>+        Local
>+        ServiceEndpoint
>+        Timer
>+        MessageEndpoint
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Home"/>
>+        <xsd:enumeration value="Remote"/>
>+        <xsd:enumeration value="LocalHome"/>
>+        <xsd:enumeration value="Local"/>
>+        <xsd:enumeration value="ServiceEndpoint"/>
>+        <xsd:enumeration value="Timer"/>
>+        <xsd:enumeration value="MessageEndpoint"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="method-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The method-nameType contains a name of an enterprise
>+        bean method or the asterisk (*) character. The asterisk is
>+        used when the element denotes all the methods of an
>+        enterprise bean's client view interfaces.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="method-paramsType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The method-paramsType defines a list of the
>+        fully-qualified Java type names of the method parameters.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="method-param"
>+                   type="javaee:java-typeType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The method-param element contains a primitive
>+            or a fully-qualified Java type name of a method
>+            parameter.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="method-permissionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The method-permissionType specifies that one or more
>+        security roles are allowed to invoke one or more enterprise
>+        bean methods. The method-permissionType consists of an
>+        optional description, a list of security role names or an
>+        indicator to state that the method is unchecked for
>+        authorization, and a list of method elements.
>+        
>+        The security roles used in the method-permissionType
>+        must be defined in the security-role elements of the
>+        deployment descriptor, and the methods must be methods
>+        defined in the enterprise bean's business, home, component 
>+        and/or web service endpoint interfaces.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:choice>
>+        <xsd:element name="role-name"
>+                     type="javaee:role-nameType"
>+                     maxOccurs="unbounded"/>
>+        <xsd:element name="unchecked"
>+                     type="javaee:emptyType">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The unchecked element specifies that a method is
>+              not checked for authorization by the container
>+              prior to invocation of the method.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+      </xsd:choice>
>+      <xsd:element name="method"
>+                   type="javaee:methodType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="multiplicityType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The multiplicityType describes the multiplicity of the
>+        role that participates in a relation.
>+        
>+        The value must be one of the two following:
>+        
>+        One
>+        Many
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="One"/>
>+        <xsd:enumeration value="Many"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="persistence-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The persistence-typeType specifies an entity bean's persistence
>+        management type.
>+        
>+        The persistence-type element must be one of the two following:
>+        
>+        Bean
>+        Container
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Bean"/>
>+        <xsd:enumeration value="Container"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="queryType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The queryType defines a finder or select
>+        query. It contains
>+        - an optional description of the query
>+        - the specification of the finder or select
>+        method it is used by
>+        	- an optional specification of the result type 
>+        	  mapping, if the query is for a select method 
>+        	  and entity objects are returned.
>+        	- the EJB QL query string that defines the query.
>+        
>+        Queries that are expressible in EJB QL must use the ejb-ql
>+        element to specify the query. If a query is not expressible
>+        in EJB QL, the description element should be used to
>+        describe the semantics of the query and the ejb-ql element
>+        should be empty.
>+        
>+        The result-type-mapping is an optional element. It can only
>+        be present if the query-method specifies a select method
>+        that returns entity objects.  The default value for the
>+        result-type-mapping element is "Local".
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"/>
>+      <xsd:element name="query-method"
>+                   type="javaee:query-methodType"/>
>+      <xsd:element name="result-type-mapping"
>+                   type="javaee:result-type-mappingType"
>+                   minOccurs="0"/>
>+      <xsd:element name="ejb-ql"
>+                   type="javaee:xsdStringType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="query-methodType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The query-method specifies the method for a finder or select
>+        query.
>+        
>+        The method-name element specifies the name of a finder or select
>+        method in the entity bean's implementation class.
>+        
>+        Each method-param must be defined for a query-method using the
>+        method-params element.
>+        
>+        It is used by the query-method element. 
>+        
>+        Example:
>+        
>+        <query>
>+        <description>Method finds large orders</description>
>+        <query-method>
>+        	  <method-name>findLargeOrders</method-name>
>+        	  <method-params></method-params>
>+        </query-method>
>+        <ejb-ql>
>+        	SELECT OBJECT(o) FROM Order o
>+        	  WHERE o.amount &gt; 1000
>+        </ejb-ql>
>+        </query>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="method-name"
>+                   type="javaee:method-nameType"/>
>+      <xsd:element name="method-params"
>+                   type="javaee:method-paramsType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="relationship-role-sourceType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The relationship-role-sourceType designates the source of a
>+        role that participates in a relationship. A
>+        relationship-role-sourceType is used by
>+        relationship-role-source elements to uniquely identify an
>+        entity bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-nameType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="relationshipsType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The relationshipsType describes the relationships in
>+        which entity beans with container-managed persistence
>+        participate. The relationshipsType contains an optional
>+        description; and a list of ejb-relation elements, which
>+        specify the container managed relationships.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-relation"
>+                   type="javaee:ejb-relationType"
>+                   maxOccurs="unbounded">
>+        <xsd:unique name="role-name-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The ejb-relationship-role-name contains the name of a
>+              relationship role. The name must be unique within 
>+              a relationship, but can be reused in different
>+              relationships.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath=".//javaee:ejb-relationship-role-name"/>
>+          <xsd:field xpath="."/>
>+        </xsd:unique>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="result-type-mappingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The result-type-mappingType is used in the query element to
>+        specify whether an abstract schema type returned by a query
>+        for a select method is to be mapped to an EJBLocalObject or
>+        EJBObject type.
>+        
>+        The value must be one of the following:
>+        
>+        Local
>+        Remote
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Local"/>
>+        <xsd:enumeration value="Remote"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="security-identityType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The security-identityType specifies whether the caller's
>+        security identity is to be used for the execution of the
>+        methods of the enterprise bean or whether a specific run-as
>+        identity is to be used. It contains an optional description
>+        and a specification of the security identity to be used.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:choice>
>+        <xsd:element name="use-caller-identity"
>+                     type="javaee:emptyType">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The use-caller-identity element specifies that
>+              the caller's security identity be used as the
>+              security identity for the execution of the
>+              enterprise bean's methods.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="run-as"
>+                     type="javaee:run-asType"/>
>+      </xsd:choice>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="session-beanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The session-beanType declares an session bean. The
>+        declaration consists of:
>+        
>+        - an optional description
>+        - an optional display name
>+        - an optional icon element that contains a small and a large 
>+        icon file name
>+        - a name assigned to the enterprise bean
>+        in the deployment description
>+        - an optional mapped-name element that can be used to provide
>+        vendor-specific deployment information such as the physical
>+        jndi-name of the session bean's remote home/business interface. 
>+        This element is not required to be supported by all 
>+        implementations. Any use of this element is non-portable.
>+        - the names of all the remote or local business interfaces, 
>+        if any
>+        - the names of the session bean's remote home and
>+        remote interfaces, if any
>+        - the names of the session bean's local home and
>+        local interfaces, if any
>+        - an optional declaration that this bean exposes a
>+        no-interface view
>+        - the name of the session bean's web service endpoint
>+        interface, if any
>+        - the session bean's implementation class
>+        - the session bean's state management type
>+        - an optional declaration of a stateful session bean's timeout value
>+        - an optional declaration of the session bean's timeout method for
>+        handling programmatically created timers
>+        - an optional declaration of timers to be automatically created at
>+        deployment time
>+        - an optional declaration that a Singleton bean has eager
>+        initialization
>+        - an optional declaration of a Singleton/Stateful bean's concurrency 
>+        management type
>+        - an optional declaration of the method locking metadata
>+        for a Singleton with container managed concurrency
>+        - an optional declaration of the other Singleton beans in the
>+        application that must be initialized before this bean
>+        - an optional declaration of the session bean's asynchronous 
>+        methods
>+        - the optional session bean's transaction management type. 
>+        If it is not present, it is defaulted to Container.
>+        - an optional declaration of a stateful session bean's 
>+        afterBegin, beforeCompletion, and/or afterCompletion methods
>+        - an optional list of the session bean class and/or
>+        superclass around-invoke methods.
>+        - an optional list of the session bean class and/or
>+        superclass around-timeout methods.
>+        - an optional declaration of the bean's 
>+        environment entries
>+        - an optional declaration of the bean's EJB references
>+        - an optional declaration of the bean's local 
>+        EJB references
>+        - an optional declaration of the bean's web 
>+        service references
>+        - an optional declaration of the security role 
>+        references
>+        - an optional declaration of the security identity 
>+        to be used for the execution of the bean's methods
>+        - an optional declaration of the bean's resource 
>+        manager connection factory references
>+        - an optional declaration of the bean's resource 
>+        environment references.
>+        - an optional declaration of the bean's message 
>+        destination references
>+        
>+        The elements that are optional are "optional" in the sense
>+        that they are omitted when if lists represented by them are
>+        empty.
>+        
>+        The service-endpoint element may only be specified if the
>+        bean is a stateless session bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="ejb-name"
>+                   type="javaee:ejb-nameType"/>
>+      <xsd:element name="mapped-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0"/>
>+      <xsd:element name="home"
>+                   type="javaee:homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="remote"
>+                   type="javaee:remoteType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local-home"
>+                   type="javaee:local-homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local"
>+                   type="javaee:localType"
>+                   minOccurs="0"/>
>+      <xsd:element name="business-local"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="business-remote"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="local-bean"
>+                   type="javaee:emptyType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The local-bean element declares that this
>+            session bean exposes a no-interface Local client view.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-endpoint"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-endpoint element contains the
>+            fully-qualified name of the enterprise bean's web
>+            service endpoint interface. The service-endpoint
>+            element may only be specified for a stateless
>+            session bean. The specified interface must be a
>+            valid JAX-RPC service endpoint interface.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="ejb-class"
>+                   type="javaee:ejb-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The ejb-class element specifies the fully qualified name
>+            of the bean class for this ejb.  It is required unless
>+            there is a component-defining annotation for the same
>+            ejb-name.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="session-type"
>+                   type="javaee:session-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="stateful-timeout"
>+                   type="javaee:stateful-timeoutType"
>+                   minOccurs="0"/>
>+      <xsd:element name="timeout-method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The timeout-method element specifies the method that
>+            will receive callbacks for programmatically
>+            created timers.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="timer"
>+                   type="javaee:timerType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="init-on-startup"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The init-on-startup element specifies that a Singleton
>+            bean has eager initialization.
>+            This element can only be specified for singleton session
>+            beans.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="concurrency-management-type"
>+                   type="javaee:concurrency-management-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="concurrent-method"
>+                   type="javaee:concurrent-methodType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="depends-on"
>+                   type="javaee:depends-onType"
>+                   minOccurs="0"/>
>+      <xsd:element name="init-method"
>+                   type="javaee:init-methodType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The init-method element specifies the mappings for
>+            EJB 2.x style create methods for an EJB 3.x bean.
>+            This element can only be specified for stateful 
>+            session beans. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="remove-method"
>+                   type="javaee:remove-methodType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The remove-method element specifies the mappings for
>+            EJB 2.x style remove methods for an EJB 3.x bean.
>+            This element can only be specified for stateful 
>+            session beans. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="async-method"
>+                   type="javaee:async-methodType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="transaction-type"
>+                   type="javaee:transaction-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="after-begin-method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0"/>
>+      <xsd:element name="before-completion-method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0"/>
>+      <xsd:element name="after-completion-method"
>+                   type="javaee:named-methodType"
>+                   minOccurs="0"/>
>+      <xsd:element name="around-invoke"
>+                   type="javaee:around-invokeType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="around-timeout"
>+                   type="javaee:around-timeoutType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>+      <xsd:element name="post-activate"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="pre-passivate"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="security-role-ref"
>+                   type="javaee:security-role-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+      </xsd:element>
>+      <xsd:element name="security-identity"
>+                   type="javaee:security-identityType"
>+                   minOccurs="0">
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="session-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The session-typeType describes whether the session bean is a
>+        singleton, stateful or stateless session. It is used by
>+        session-type elements.
>+        
>+        The value must be one of the three following:
>+        
>+        Singleton
>+        Stateful
>+        Stateless
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Singleton"/>
>+        <xsd:enumeration value="Stateful"/>
>+        <xsd:enumeration value="Stateless"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="stateful-timeoutType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The stateful-timeoutType represents the amount of time
>+        a stateful session bean can be idle(not receive any client
>+        invocations) before it is eligible for removal by the container.
>+        
>+        A timeout value of 0 means the bean is immediately eligible for removal.
>+        
>+        A timeout value of -1 means the bean will never be removed due to timeout.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="timeout"
>+                   type="javaee:xsdIntegerType"/>
>+      <xsd:element name="unit"
>+                   type="javaee:time-unit-typeType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="time-unit-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The time-unit-typeType represents a time duration at a given
>+        unit of granularity.  
>+        
>+        The time unit type must be one of the following :
>+        
>+        Days
>+        Hours
>+        Minutes
>+        Seconds
>+        Milliseconds
>+        Microseconds
>+        Nanoseconds
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Days"/>
>+        <xsd:enumeration value="Hours"/>
>+        <xsd:enumeration value="Minutes"/>
>+        <xsd:enumeration value="Seconds"/>
>+        <xsd:enumeration value="Milliseconds"/>
>+        <xsd:enumeration value="Microseconds"/>
>+        <xsd:enumeration value="Nanoseconds"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="timer-scheduleType">
>+    <xsd:sequence>
>+      <xsd:element name="second"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="minute"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="hour"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="day-of-month"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="month"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="day-of-week"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="year"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="timerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The timerType specifies an enterprise bean timer.  Each
>+        timer is automatically created by the container upon
>+        deployment.  Timer callbacks occur based on the 
>+        schedule attributes.  All callbacks are made to the
>+        timeout-method associated with the timer.  
>+        
>+        A timer can have an optional start and/or end date. If
>+        a start date is specified, it takes precedence over the
>+        associated timer schedule such that any matching
>+        expirations prior to the start time will not occur.
>+        Likewise, no matching expirations will occur after any
>+        end date.   Start/End dates are specified using the
>+        XML Schema dateTime type, which follows the ISO-8601
>+        standard for date(and optional time-within-the-day) 
>+        representation.
>+        
>+        An optional flag can be used to control whether
>+        this timer has persistent(true) delivery semantics or
>+        non-persistent(false) delivery semantics.  If not specified,
>+        the value defaults to persistent(true).
>+        
>+        A time zone can optionally be associated with a timer.
>+        If specified, the timer's schedule is evaluated in the context
>+        of that time zone, regardless of the default time zone in which
>+        the container is executing.   Time zones are specified as an
>+        ID string.  The set of required time zone IDs is defined by
>+        the Zone Name(TZ) column of the public domain zoneinfo database.
>+        
>+        An optional info string can be assigned to the timer and 
>+        retrieved at runtime through the Timer.getInfo() method.
>+        
>+        The timerType can only be specified on stateless session
>+        beans, singleton session beans, and message-driven beans.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="schedule"
>+                   type="javaee:timer-scheduleType"/>
>+      <xsd:element name="start"
>+                   type="xsd:dateTime"
>+                   minOccurs="0"/>
>+      <xsd:element name="end"
>+                   type="xsd:dateTime"
>+                   minOccurs="0"/>
>+      <xsd:element name="timeout-method"
>+                   type="javaee:named-methodType"/>
>+      <xsd:element name="persistent"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="timezone"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:element name="info"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="trans-attributeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The trans-attributeType specifies how the container must
>+        manage the transaction boundaries when delegating a method 
>+        invocation to an enterprise bean's business method. 
>+        
>+        The value must be one of the following: 
>+        
>+        NotSupported 
>+        Supports 
>+        Required  
>+        RequiresNew 
>+        Mandatory 
>+        Never 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="NotSupported"/>
>+        <xsd:enumeration value="Supports"/>
>+        <xsd:enumeration value="Required"/>
>+        <xsd:enumeration value="RequiresNew"/>
>+        <xsd:enumeration value="Mandatory"/>
>+        <xsd:enumeration value="Never"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="transaction-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The transaction-typeType specifies an enterprise bean's
>+        transaction management type.
>+        
>+        The transaction-type must be one of the two following:
>+        
>+        Bean
>+        Container
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Bean"/>
>+        <xsd:enumeration value="Container"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/web-fragment_3_0.xsd
>===================================================================
>RCS file: dtdsAndSchemas/web-fragment_3_0.xsd
>diff -N dtdsAndSchemas/web-fragment_3_0.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/web-fragment_3_0.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,272 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="3.0">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the Servlet 3.0 deployment descriptor.
>+      The deployment descriptor must be named "META-INF/web-fragment.xml"
>+      in the web fragment's jar 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-fragment xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="..."
>+      version="3.0"> 
>+      ...
>+      </web-fragment>
>+      
>+      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-fragment_3_0.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="web-common_3_0.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="web-fragment"
>+               type="javaee:web-fragmentType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The web-fragment element is the root of the deployment
>+        descriptor for a web fragment.  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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-role-name-references"
>+                refer="javaee:web-common-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:schema>
>Index: dtdsAndSchemas/application-client_6.xsd
>===================================================================
>RCS file: dtdsAndSchemas/application-client_6.xsd
>diff -N dtdsAndSchemas/application-client_6.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/application-client_6.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,311 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="6">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the application client 6
>+      deployment descriptor.  The deployment descriptor must
>+      be named "META-INF/application-client.xml" in the
>+      application client's jar file.  All application client
>+      deployment descriptors must indicate the application
>+      client schema by using the Java EE namespace:
>+      
>+      http://java.sun.com/xml/ns/javaee
>+      
>+      and indicate the version of the schema by
>+      using the version element as shown below:
>+      
>+      <application-client xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
>+      	http://java.sun.com/xml/ns/javaee/application-client_6.xsd"
>+      version="6">
>+      ...
>+      </application-client>
>+      
>+      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/application-client_6.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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="application-client"
>+               type="javaee:application-clientType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The application-client element is the root element of an
>+        application client deployment descriptor.  The application
>+        client deployment descriptor describes the EJB components
>+        and external resources referenced by the application
>+        client.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:unique name="env-entry-name-uniqueness">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The env-entry-name element contains the name of an
>+          application client's environment entry.  The name is a JNDI
>+          name relative to the java:comp/env context.  The name must
>+          be unique within an application client.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:env-entry"/>
>+      <xsd:field xpath="javaee:env-entry-name"/>
>+    </xsd:unique>
>+    <xsd:unique name="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 application
>+          client's environment and is relative to the
>+          java:comp/env context. The name must be unique within the
>+          application client.
>+          
>+          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="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 an application client.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:resource-ref"/>
>+      <xsd:field xpath="javaee:res-ref-name"/>
>+    </xsd:unique>
>+    <xsd:unique name="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 application client
>+          code. The name is a JNDI name relative to the
>+          java:comp/env context and must be unique within an
>+          application client.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:resource-env-ref"/>
>+      <xsd:field xpath="javaee:resource-env-ref-name"/>
>+    </xsd:unique>
>+    <xsd:unique name="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 message destination reference name used in the
>+          application client code. The name is a JNDI name
>+          relative to the java:comp/env context and must be unique
>+          within an application client.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:message-destination-ref"/>
>+      <xsd:field xpath="javaee:message-destination-ref-name"/>
>+    </xsd:unique>
>+  </xsd:element>
>+
>+
>+
>+
>+  <xsd:complexType name="application-clientType">
>+    <xsd:sequence>
>+      <xsd:element name="module-name"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="env-entry"
>+                   type="javaee:env-entryType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-ref"
>+                   type="javaee:ejb-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:service-refGroup"/>
>+      <xsd:element name="resource-ref"
>+                   type="javaee:resource-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="resource-env-ref"
>+                   type="javaee:resource-env-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination-ref"
>+                   type="javaee:message-destination-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-unit-ref"
>+                   type="javaee:persistence-unit-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="post-construct"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="pre-destroy"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="callback-handler"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The callback-handler element names a class provided by
>+            the application.  The class must have a no args
>+            constructor and must implement the
>+            javax.security.auth.callback.CallbackHandler
>+            interface.  The class will be instantiated by the
>+            application client container and used by the container
>+            to collect authentication information from the user.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="message-destination"
>+                   type="javaee:message-destinationType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="data-source"
>+                   type="javaee:data-sourceType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="version"
>+                   type="javaee:dewey-versionType"
>+                   fixed="6"
>+                   use="required">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The required value for the version is 6.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <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:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/connector_1_6.xsd
>===================================================================
>RCS file: dtdsAndSchemas/connector_1_6.xsd
>diff -N dtdsAndSchemas/connector_1_6.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/connector_1_6.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,1261 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="1.6">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the Connector 1.6 deployment
>+      descriptor.  The deployment descriptor must be named
>+      "META-INF/ra.xml" in the connector's rar file.  All Connector
>+      deployment descriptors must indicate the connector resource
>+      adapter 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:
>+      
>+      <connector xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>+      	 http://java.sun.com/xml/ns/javaee/connector_1_6.xsd"
>+      version="1.6">
>+      ...
>+      </connector>
>+      
>+      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/connector_1_6.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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="connector"
>+               type="javaee:connectorType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The connector element is the root element of the deployment
>+        descriptor for the resource adapter. This element includes
>+        general information - vendor name, resource adapter version,
>+        icon - about the resource adapter module. It also includes
>+        information specific to the implementation of the resource
>+        adapter library as specified through the element
>+        resourceadapter.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+  </xsd:element>
>+
>+
>+
>+
>+  <xsd:complexType name="activationspecType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The activationspecType specifies an activation
>+        specification.  The information includes fully qualified
>+        Java class name of an activation specification and a set of
>+        required configuration property names.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="activationspec-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element activationspec-class specifies the fully
>+            qualified Java class name of the activation
>+            specification class. This class must implement the
>+            javax.resource.spi.ActivationSpec interface. The
>+            implementation of this class is required to be a
>+            JavaBean.
>+            
>+            Example:
>+            	  <activationspec-class>com.wombat.ActivationSpecImpl
>+            	  </activationspec-class>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="required-config-property"
>+                   type="javaee:required-config-propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The required-config-property element is deprecated since
>+            Connectors 1.6 specification. The resource adapter 
>+            implementation is recommended to use the @NotNull
>+            Bean Validation annotation or its XML validation
>+            descriptor equivalent to indicate that a configuration
>+            property is required to be specified by the deployer.
>+            See the Connectors specification for more information. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property"
>+                   type="javaee:config-propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="adminobjectType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The adminobjectType specifies information about an
>+        administered object.  Administered objects are specific to a
>+        messaging style or message provider.  This contains
>+        information on the Java type of the interface implemented by
>+        an administered object, its Java class name and its
>+        configuration properties.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="adminobject-interface"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element adminobject-interface specifies the
>+            fully qualified name of the Java type of the
>+            interface implemented by an administered object.
>+            
>+            Example:
>+            	<adminobject-interface>javax.jms.Destination
>+            	</adminobject-interface>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="adminobject-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element adminobject-class specifies the fully
>+            qualified Java class name of an administered object.
>+            
>+            Example:
>+            	  <adminobject-class>com.wombat.DestinationImpl
>+            	  </adminobject-class>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property"
>+                   type="javaee:config-propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="authentication-mechanismType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The authentication-mechanismType specifies an authentication
>+        mechanism supported by the resource adapter. Note that this
>+        support is for the resource adapter and not for the
>+        underlying EIS instance. The optional description specifies
>+        any resource adapter specific requirement for the support of
>+        security contract and authentication mechanism.
>+        
>+        Note that BasicPassword mechanism type should support the
>+        javax.resource.spi.security.PasswordCredential interface.
>+        The Kerbv5 mechanism type should support the
>+        org.ietf.jgss.GSSCredential interface or the deprecated
>+        javax.resource.spi.security.GenericCredential interface.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="authentication-mechanism-type"
>+                   type="javaee:xsdStringType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element authentication-mechanism-type specifies
>+            type of an authentication mechanism.
>+            
>+            The example values are:
>+            
>+            <authentication-mechanism-type>BasicPassword
>+            </authentication-mechanism-type>
>+            
>+            <authentication-mechanism-type>Kerbv5
>+            </authentication-mechanism-type>
>+            
>+            Any additional security mechanisms are outside the
>+            scope of the Connector architecture specification.
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="credential-interface"
>+                   type="javaee:credential-interfaceType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="config-property-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The config-property-nameType contains the name of a
>+        configuration property.
>+        
>+        The connector architecture defines a set of well-defined
>+        properties all of type java.lang.String. These are as
>+        follows.
>+        
>+        ServerName
>+        PortNumber
>+        UserName
>+        Password
>+        ConnectionURL
>+        
>+        A resource adapter provider can extend this property set to
>+        include properties specific to the resource adapter and its
>+        underlying EIS.
>+        
>+        Possible values include
>+        	  ServerName
>+        	  PortNumber
>+        	  UserName
>+        	  Password
>+        	  ConnectionURL
>+        
>+        Example: <config-property-name>ServerName</config-property-name>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:xsdStringType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="config-property-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The config-property-typeType contains the fully
>+        qualified Java type of a configuration property.
>+        
>+        The following are the legal values:
>+        java.lang.Boolean, java.lang.String, java.lang.Integer,
>+        java.lang.Double, java.lang.Byte, java.lang.Short,
>+        java.lang.Long, java.lang.Float, java.lang.Character
>+        
>+        Used in: config-property
>+        
>+        Example:
>+        <config-property-type>java.lang.String</config-property-type>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="java.lang.Boolean"/>
>+        <xsd:enumeration value="java.lang.String"/>
>+        <xsd:enumeration value="java.lang.Integer"/>
>+        <xsd:enumeration value="java.lang.Double"/>
>+        <xsd:enumeration value="java.lang.Byte"/>
>+        <xsd:enumeration value="java.lang.Short"/>
>+        <xsd:enumeration value="java.lang.Long"/>
>+        <xsd:enumeration value="java.lang.Float"/>
>+        <xsd:enumeration value="java.lang.Character"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="config-propertyType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The config-propertyType contains a declaration of a single
>+        configuration property that may be used for providing
>+        configuration information.
>+        
>+        The declaration consists of an optional description, name,
>+        type and an optional value of the configuration property. If
>+        the resource adapter provider does not specify a value than
>+        the deployer is responsible for providing a valid value for
>+        a configuration property.
>+        
>+        Any bounds or well-defined values of properties should be
>+        described in the description element.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="config-property-name"
>+                   type="javaee:config-property-nameType"/>
>+      <xsd:element name="config-property-type"
>+                   type="javaee:config-property-typeType"/>
>+      <xsd:element name="config-property-value"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element config-property-value contains the value
>+            of a configuration entry. Note, it is possible for a
>+            resource adapter deployer to override this
>+            configuration information during deployment.
>+            
>+            Example:
>+            <config-property-value>WombatServer</config-property-value>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property-ignore"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element config-property-ignore is used to specify 
>+            whether the configuration tools must ignore considering the 
>+            configuration property during auto-discovery of
>+            Configuration properties. See the Connector specification for
>+            more details. If unspecified, the container must not ignore
>+            the configuration property during auto-discovery.
>+            This element must be one of the following, "true" or "false".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property-supports-dynamic-updates"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element config-property-supports-dynamic-updates is used to specify 
>+            whether the configuration property allows its value to be updated, by
>+            application server's configuration tools, during the lifetime of
>+            the JavaBean instance. See the Connector specification for
>+            more details. If unspecified, the container must not dynamically
>+            reconfigure the property.
>+            This element must be one of the following, "true" or "false".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property-confidential"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element config-property-confidential is used to specify 
>+            whether the configuration property is confidential and
>+            recommends application server's configuration tools to use special 
>+            visual aids for editing them. See the Connector specification for
>+            more details. If unspecified, the container must not treat the
>+            property as confidential.
>+            This element must be one of the following, "true" or "false".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="connection-definitionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The connection-definitionType defines a set of connection
>+        interfaces and classes pertaining to a particular connection
>+        type. This also includes configurable properties for
>+        ManagedConnectionFactory instances that may be produced out
>+        of this set.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="managedconnectionfactory-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element managedconnectionfactory-class specifies
>+            the fully qualified name of the Java class that
>+            implements the
>+            javax.resource.spi.ManagedConnectionFactory interface.
>+            This Java class is provided as part of resource
>+            adapter's implementation of connector architecture
>+            specified contracts. The implementation of this
>+            class is required to be a JavaBean.
>+            
>+            Example:
>+            <managedconnectionfactory-class>
>+            	  com.wombat.ManagedConnectionFactoryImpl
>+            </managedconnectionfactory-class>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property"
>+                   type="javaee:config-propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="connectionfactory-interface"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element connectionfactory-interface specifies
>+            the fully qualified name of the ConnectionFactory
>+            interface supported by the resource adapter.
>+            
>+            Example:
>+            <connectionfactory-interface>com.wombat.ConnectionFactory
>+            </connectionfactory-interface>
>+            
>+            OR
>+            
>+            <connectionfactory-interface>javax.resource.cci.ConnectionFactory
>+            </connectionfactory-interface>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="connectionfactory-impl-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element connectionfactory-impl-class specifies
>+            the fully qualified name of the ConnectionFactory
>+            class that implements resource adapter
>+            specific ConnectionFactory interface.
>+            
>+            Example:
>+            
>+            <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl
>+            </connectionfactory-impl-class>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="connection-interface"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The connection-interface element specifies the fully
>+            qualified name of the Connection interface supported
>+            by the resource adapter.
>+            
>+            Example:
>+            
>+            	  <connection-interface>javax.resource.cci.Connection
>+            	  </connection-interface>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="connection-impl-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The connection-impl-classType specifies the fully
>+            qualified name of the Connection class that
>+            implements resource adapter specific Connection
>+            interface.  It is used by the connection-impl-class
>+            elements.
>+            
>+            Example:
>+            
>+            	  <connection-impl-class>com.wombat.ConnectionImpl
>+            	  </connection-impl-class>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="connectorType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The connectorType defines a resource adapter.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="module-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element module-name specifies the name of the
>+            resource adapter.
>+            
>+            If there is no module-name specified, the module-name
>+            is determined as defined in Section EE.8.1.1 and EE.8.1.2 
>+            of the Java Platform, Enterprise Edition (Java EE) 
>+            Specification, version 6.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="vendor-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element vendor-name specifies the name of
>+            resource adapter provider vendor.
>+            
>+            If there is no vendor-name specified, the application 
>+            server must consider the default "" (empty string) as
>+            the name of the resource adapter provider vendor.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="eis-type"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element eis-type contains information about the
>+            type of the EIS. For example, the type of an EIS can
>+            be product name of EIS independent of any version
>+            info.
>+            
>+            This helps in identifying EIS instances that can be
>+            used with this resource adapter.
>+            
>+            If there is no eis-type specified, the application 
>+            server must consider the default "" (empty string) as
>+            the type of the EIS.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="resourceadapter-version"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element resourceadapter-version specifies a string-based version
>+            of the resource adapter from the resource adapter
>+            provider.
>+            
>+            If there is no resourceadapter-version specified, the application 
>+            server must consider the default "" (empty string) as
>+            the version of the resource adapter.
>+            	
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="license"
>+                   type="javaee:licenseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="resourceadapter"
>+                   type="javaee:resourceadapterType"/>
>+      <xsd:element name="required-work-context"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element required-work-context specifies a fully qualified class 
>+            name that implements WorkContext interface, that the resource adapter 
>+            requires the application server to support.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="version"
>+                   type="javaee:dewey-versionType"
>+                   fixed="1.6"
>+                   use="required">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The version indicates the version of the schema to be used by the
>+          deployment tool. This element doesn't have a default, and the resource adapter 
>+          developer/deployer is required to specify it. The element allows the deployment 
>+          tool to choose which schema to validate the descriptor against.
>+          	  
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <xsd:attribute name="metadata-complete"
>+                   type="xsd:boolean">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The metadata-complete attribute defines whether the deployment 
>+          descriptor for the resource adapter module is complete, or whether
>+          the class files available to the module and packaged with the resource 
>+          adapter should be examined for annotations that specify deployment 
>+          information.
>+          
>+          If metadata-complete is set to "true", the deployment tool of the 
>+          application server 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 this specification. If the 
>+          deployment descriptor is not included or is included but not marked 
>+          metadata-complete, the deployment tool will process annotations.
>+          
>+          Application servers must assume that metadata-complete is true for 
>+          resource adapter modules with deployment descriptor version 
>+          lower than 1.6.
>+          		
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="credential-interfaceType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The credential-interfaceType specifies the
>+        interface that the resource adapter implementation
>+        supports for the representation of the
>+        credentials. This element(s) that use this type,
>+        i.e. credential-interface,  should be used by
>+        application server to find out the Credential
>+        interface it should use as part of the security
>+        contract.
>+        
>+        The possible values are:
>+        
>+        javax.resource.spi.security.PasswordCredential
>+        org.ietf.jgss.GSSCredential
>+        javax.resource.spi.security.GenericCredential
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType">
>+        <xsd:enumeration value="javax.resource.spi.security.PasswordCredential"/>
>+        <xsd:enumeration value="org.ietf.jgss.GSSCredential"/>
>+        <xsd:enumeration value="javax.resource.spi.security.GenericCredential"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="inbound-resourceadapterType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The inbound-resourceadapterType specifies information
>+        about an inbound resource adapter. This contains information
>+        specific to the implementation of the resource adapter
>+        library as specified through the messageadapter element.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="messageadapter"
>+                   type="javaee:messageadapterType"
>+                   minOccurs="0">
>+        <xsd:unique name="messagelistener-type-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The messagelistener-type element content must be
>+              unique in the messageadapter. Several messagelisteners
>+              can not use the same messagelistener-type.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:messagelistener"/>
>+          <xsd:field xpath="javaee:messagelistener-type"/>
>+        </xsd:unique>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="licenseType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The licenseType specifies licensing requirements for the
>+        resource adapter module. This type specifies whether a
>+        license is required to deploy and use this resource adapter,
>+        and an optional description of the licensing terms
>+        (examples: duration of license, number of connection
>+        restrictions). It is used by the license element.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="license-required"
>+                   type="javaee:true-falseType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element license-required specifies whether a
>+            license is required to deploy and use the
>+            resource adapter. This element must be one of
>+            the following, "true" or "false".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="messageadapterType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The messageadapterType specifies information about the
>+        messaging capabilities of the resource adapter. This
>+        contains information specific to the implementation of the
>+        resource adapter library as specified through the
>+        messagelistener element.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="messagelistener"
>+                   type="javaee:messagelistenerType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="messagelistenerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The messagelistenerType specifies information about a
>+        specific message listener supported by the messaging
>+        resource adapter. It contains information on the Java type
>+        of the message listener interface and an activation
>+        specification.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="messagelistener-type"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The element messagelistener-type specifies the fully
>+            qualified name of the Java type of a message
>+            listener interface.
>+            
>+            Example:
>+            
>+            	<messagelistener-type>javax.jms.MessageListener
>+            	</messagelistener-type>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="activationspec"
>+                   type="javaee:activationspecType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="outbound-resourceadapterType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The outbound-resourceadapterType specifies information about
>+        an outbound resource adapter. The information includes fully
>+        qualified names of classes/interfaces required as part of
>+        the connector architecture specified contracts for
>+        connection management, level of transaction support
>+        provided, one or more authentication mechanisms supported
>+        and additional required security permissions.
>+        
>+        If any of the outbound resource adapter elements (transaction-support,
>+        authentication-mechanism, reauthentication-support) is specified through
>+        this element or metadata annotations, and no  connection-definition is 
>+        specified as part of this element or through annotations, the 
>+        application server must consider this an error and fail deployment. 
>+        
>+        If there is no authentication-mechanism specified as part of
>+        this element or metadata annotations, then the resource adapter does 
>+        not support any standard security authentication mechanisms as 
>+        part of security contract. The application server ignores the security 
>+        part of the system contracts in this case.
>+        
>+        If there is no transaction-support specified as part of this element 
>+        or metadata annotation, then the application server must consider that 
>+        the resource adapter does not support either the resource manager local 
>+        or JTA transactions and must consider the transaction support as 
>+        NoTransaction. Note that resource adapters may specify the level of 
>+        transaction support to be used at runtime for a ManagedConnectionFactory 
>+        through the TransactionSupport interface.
>+        
>+        If there is no reauthentication-support specified as part of
>+        this element or metadata annotation, then the application server must consider 
>+        that the resource adapter does not support re-authentication of 
>+        ManagedConnections.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="connection-definition"
>+                   type="javaee:connection-definitionType"
>+                   maxOccurs="unbounded"
>+                   minOccurs="0"/>
>+      <xsd:element name="transaction-support"
>+                   type="javaee:transaction-supportType"
>+                   minOccurs="0"/>
>+      <xsd:element name="authentication-mechanism"
>+                   type="javaee:authentication-mechanismType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="reauthentication-support"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            	    The element reauthentication-support specifies
>+            	    whether the resource adapter implementation supports
>+            	    re-authentication of existing Managed- Connection
>+            	    instance. Note that this information is for the
>+            	    resource adapter implementation and not for the
>+            	    underlying EIS instance. This element must have
>+            	    either a "true" or "false" value.
>+            
>+            	  
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="required-config-propertyType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The required-config-propertyType contains a declaration
>+        of a single configuration property used for specifying a
>+        required configuration property name. It is used
>+        by required-config-property elements.
>+        
>+        Usage of this type is deprecated from Connectors 1.6 specification. 
>+        Refer to required-config-property element for more information.
>+        
>+        Example:
>+        
>+        <required-config-property>
>+        <config-property-name>Destination</config-property-name>
>+        </required-config-property>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="config-property-name"
>+                   type="javaee:config-property-nameType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="resourceadapterType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The resourceadapterType specifies information about the
>+        resource adapter. The information includes fully qualified
>+        resource adapter Java class name, configuration properties,
>+        information specific to the implementation of the resource
>+        adapter library as specified through the
>+        outbound-resourceadapter and inbound-resourceadapter
>+        elements, and an optional set of administered objects.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="resourceadapter-class"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element resourceadapter-class specifies the
>+            fully qualified name of a Java class that implements
>+            the javax.resource.spi.ResourceAdapter
>+            interface. This Java class is provided as part of
>+            resource adapter's implementation of connector
>+            architecture specified contracts. The implementation
>+            of this class is required to be a JavaBean.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="config-property"
>+                   type="javaee:config-propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="outbound-resourceadapter"
>+                   type="javaee:outbound-resourceadapterType"
>+                   minOccurs="0">
>+        <xsd:unique name="connectionfactory-interface-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The connectionfactory-interface element content
>+              must be unique in the outbound-resourceadapter.
>+              Multiple connection-definitions can not use the
>+              same connectionfactory-type.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:connection-definition"/>
>+          <xsd:field xpath="javaee:connectionfactory-interface"/>
>+        </xsd:unique>
>+      </xsd:element>
>+      <xsd:element name="inbound-resourceadapter"
>+                   type="javaee:inbound-resourceadapterType"
>+                   minOccurs="0"/>
>+      <xsd:element name="adminobject"
>+                   type="javaee:adminobjectType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:unique name="adminobject-type-uniqueness">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The adminobject-interface and adminobject-class element content must be
>+              unique in the resourceadapterType. Several admin objects
>+              can not use the same adminobject-interface and adminobject-class.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:adminobject"/>
>+          <xsd:field xpath="javaee:adminobject-interface"/>
>+          <xsd:field xpath="javaee:adminobject-class"/>
>+        </xsd:unique>
>+      </xsd:element>
>+      <xsd:element name="security-permission"
>+                   type="javaee:security-permissionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="security-permissionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The security-permissionType specifies a security
>+        permission that is required by the resource adapter code.
>+        
>+        The security permission listed in the deployment descriptor
>+        are ones that are different from those required by the
>+        default permission set as specified in the connector
>+        specification. The optional description can mention specific
>+        reason that resource adapter requires a given security
>+        permission.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="security-permission-spec"
>+                   type="javaee:xsdStringType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The element security-permission-spec specifies a security
>+            permission based on the Security policy file
>+            syntax. Refer to the following URL for Sun's
>+            implementation of the security permission
>+            specification:
>+            
>+            http://java.sun.com/javase/6/docs/technotes/guides/security/PolicyFiles.html
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="transaction-supportType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The transaction-supportType specifies the level of
>+        transaction support provided by the resource adapter. It is
>+        used by transaction-support elements.
>+        
>+        The value must be one of the following:
>+        
>+        NoTransaction
>+        LocalTransaction
>+        XATransaction
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="NoTransaction"/>
>+        <xsd:enumeration value="LocalTransaction"/>
>+        <xsd:enumeration value="XATransaction"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/application_6.xsd
>===================================================================
>RCS file: dtdsAndSchemas/application_6.xsd
>diff -N dtdsAndSchemas/application_6.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/application_6.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,394 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="6">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the application 6 deployment
>+      descriptor.  The deployment descriptor must be named
>+      "META-INF/application.xml" in the application's ear file.
>+      All application deployment descriptors must indicate
>+      the application schema by using the Java EE namespace:
>+      
>+      http://java.sun.com/xml/ns/javaee
>+      
>+      and indicate the version of the schema by
>+      using the version element as shown below:
>+      
>+      <application xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
>+      	http://java.sun.com/xml/ns/javaee/application_6.xsd"
>+      version="6">
>+      ...
>+      </application>
>+      
>+      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/application_6.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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="application"
>+               type="javaee:applicationType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The application element is the root element of a Java EE
>+        application deployment descriptor.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:unique name="context-root-uniqueness">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The context-root element content must be unique
>+          in the ear. 
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:module/javaee:web"/>
>+      <xsd:field xpath="javaee:context-root"/>
>+    </xsd:unique>
>+    <xsd:unique name="security-role-uniqueness">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The security-role-name element content
>+          must be unique in the ear.  
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:security-role"/>
>+      <xsd:field xpath="javaee:role-name"/>
>+    </xsd:unique>
>+  </xsd:element>
>+
>+
>+
>+
>+  <xsd:complexType name="applicationType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The applicationType defines the structure of the
>+        application. 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="application-name"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="initialize-in-order"
>+                   type="javaee:generic-booleanType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            If initialize-in-order is true, modules must be initialized
>+            in the order they're listed in this deployment descriptor,
>+            with the exception of application client modules, which can
>+            be initialized in any order.
>+            If initialize-in-order is not set or set to false, the order
>+            of initialization is unspecified and may be product-dependent.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="module"
>+                   type="javaee:moduleType"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The application deployment descriptor must have one
>+            module element for each Java EE module in the
>+            application package. A module element is defined 
>+            by moduleType definition. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="security-role"
>+                   type="javaee:security-roleType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="library-directory"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The library-directory element specifies the pathname
>+            of a directory within the application package, relative
>+            to the top level of the application package.  All files
>+            named "*.jar" in this directory must be made available
>+            in the class path of all components included in this
>+            application package.  If this element isn't specified,
>+            the directory named "lib" is searched.  An empty element
>+            may be used to disable searching.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="env-entry"
>+                   type="javaee:env-entryType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-ref"
>+                   type="javaee:ejb-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-local-ref"
>+                   type="javaee:ejb-local-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:service-refGroup"/>
>+      <xsd:element name="resource-ref"
>+                   type="javaee:resource-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="resource-env-ref"
>+                   type="javaee:resource-env-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination-ref"
>+                   type="javaee:message-destination-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-context-ref"
>+                   type="javaee:persistence-context-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-unit-ref"
>+                   type="javaee:persistence-unit-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination"
>+                   type="javaee:message-destinationType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="data-source"
>+                   type="javaee:data-sourceType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="version"
>+                   type="javaee:dewey-versionType"
>+                   fixed="6"
>+                   use="required">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The required value for the version is 6.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="moduleType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The moduleType defines a single Java EE module and contains a
>+        connector, ejb, java, or web element, which indicates the
>+        module type and contains a path to the module file, and an
>+        optional alt-dd element, which specifies an optional URI to
>+        the post-assembly version of the deployment descriptor.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:choice>
>+        <xsd:element name="connector"
>+                     type="javaee:pathType">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The connector element specifies the URI of a
>+              resource adapter archive file, relative to the
>+              top level of the application package.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="ejb"
>+                     type="javaee:pathType">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The ejb element specifies the URI of an ejb-jar,
>+              relative to the top level of the application
>+              package.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="java"
>+                     type="javaee:pathType">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              The java element specifies the URI of a java
>+              application client module, relative to the top
>+              level of the application package.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="web"
>+                     type="javaee:webType"/>
>+      </xsd:choice>
>+      <xsd:element name="alt-dd"
>+                   type="javaee:pathType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The alt-dd element specifies an optional URI to the
>+            post-assembly version of the deployment descriptor
>+            file for a particular Java EE module.  The URI must
>+            specify the full pathname of the deployment
>+            descriptor file relative to the application's root
>+            directory. If alt-dd is not specified, the deployer
>+            must read the deployment descriptor from the default
>+            location and file name required by the respective
>+            component specification.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="webType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The webType defines the web-uri and context-root of
>+        a web application module.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="web-uri"
>+                   type="javaee:pathType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The web-uri element specifies the URI of a web
>+            application file, relative to the top level of the
>+            application package.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="context-root"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The context-root element specifies the context root
>+            of a web application.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/javaee_web_services_1_3.xsd
>===================================================================
>RCS file: dtdsAndSchemas/javaee_web_services_1_3.xsd
>diff -N dtdsAndSchemas/javaee_web_services_1_3.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/javaee_web_services_1_3.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,572 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="1.3">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      (C) Copyright International Business Machines Corporation 2002
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      The webservices element is the root element for the web services
>+      deployment descriptor.  It specifies the set of web service
>+      descriptions that are to be deployed into the Java EE Application
>+      Server and the dependencies they have on container resources and
>+      services.  The deployment descriptor must be named
>+      "META-INF/webservices.xml" in the web services' jar file.
>+      
>+      Used in: webservices.xml
>+      
>+      All webservices deployment descriptors must indicate the
>+      webservices 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:
>+      
>+      <webservices xmlns="http://java.sun.com/xml/ns/javaee"
>+      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>+      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>+      	http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.xsd"
>+      version="1.3">
>+      ...
>+      </webservices>
>+      
>+      The instance documents may indicate the published version of the
>+      schema using the xsi:schemaLocation attribute for the Java EE
>+      namespace with the following location:
>+      
>+      http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:element name="webservices"
>+               type="javaee:webservicesType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The webservices element is the root element for the web services
>+        deployment descriptor.  It specifies the set of web service
>+        descriptions that are to be deployed into the Java EE Application Server
>+        and the dependencies they have on container resources and services.
>+        
>+        Used in: webservices.xml
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:key name="webservice-description-name-key">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The webservice-description-name identifies the collection of
>+          port-components associated with a WSDL file and JAX-RPC mapping. The
>+          name must be unique within the deployment descriptor.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:selector xpath="javaee:webservice-description"/>
>+      <xsd:field xpath="javaee:webservice-description-name"/>
>+    </xsd:key>
>+  </xsd:element>
>+
>+
>+
>+
>+  <xsd:complexType name="port-componentType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The port-component element associates a WSDL port with a web service
>+        interface and implementation.  It defines the name of the port as a
>+        component, optional description, optional display name, optional iconic
>+        representations, WSDL port QName, Service Endpoint Interface, Service
>+        Implementation Bean.
>+        
>+        This element also associates a WSDL service with a JAX-WS Provider
>+        implementation.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="display-name"
>+                   type="javaee:display-nameType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="icon"
>+                   type="javaee:iconType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="port-component-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The port-component-name element specifies a port component's
>+            name.  This name is assigned by the module producer to name
>+            the service implementation bean in the module's deployment
>+            descriptor. The name must be unique among the port component
>+            names defined in the same module.
>+            
>+            Used in: port-component
>+            
>+            Example:
>+            	      <port-component-name>EmployeeService
>+            	      </port-component-name>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="wsdl-service"
>+                   type="javaee:xsdQNameType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Defines the name space and local name part of the WSDL
>+            service QName. This is required to be specified for
>+            port components that are JAX-WS Provider implementations.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="wsdl-port"
>+                   type="javaee:xsdQNameType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Defines the name space and local name part of the WSDL
>+            port QName. This is not required to be specified for port
>+            components that are JAX-WS Provider implementations
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="enable-mtom"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Used to enable or disable SOAP MTOM/XOP mechanism for an
>+            endpoint implementation.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="mtom-threshold"
>+                   type="javaee:xsdNonNegativeIntegerType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            When MTOM is enabled, binary data above this size in bytes
>+            will be XOP encoded or sent as attachment. Default value is 0.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="addressing"
>+                   type="javaee:addressingType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            This specifies the WS-Addressing requirements for a JAX-WS
>+            web service. It corresponds to javax.xml.ws.soap.Addressing
>+            annotation or its feature javax.xml.ws.soap.AddressingFeature.
>+            
>+            See the addressingType for more information.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="respect-binding"
>+                   type="javaee:respect-bindingType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Corresponds to the javax.xml.ws.RespectBinding annotation
>+            or its corresponding javax.xml.ws.RespectBindingFeature web
>+            service feature. This is used to control whether a JAX-WS
>+            implementation must respect/honor the contents of the
>+            wsdl:binding in the WSDL that is associated with the service.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="protocol-binding"
>+                   type="javaee:protocol-bindingType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Used to specify the protocol binding used by the port-component.
>+            If this element is not specified, then the default binding is
>+            used (SOAP 1.1 over HTTP)
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-endpoint-interface"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The service-endpoint-interface element contains the
>+            fully-qualified name of the port component's Service Endpoint
>+            Interface.
>+            
>+            Used in: port-component
>+            
>+            Example:
>+            	      <remote>com.wombat.empl.EmployeeService</remote>
>+            
>+            This may not be specified in case there is no Service
>+            Enpoint Interface as is the case with directly using an
>+            implementation class with the @WebService annotation.
>+            
>+            When the port component is a Provider implementation
>+            this is not specified.
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-impl-bean"
>+                   type="javaee:service-impl-beanType"/>
>+      <xsd:choice>
>+        <xsd:element name="handler"
>+                     type="javaee:handlerType"
>+                     minOccurs="0"
>+                     maxOccurs="unbounded">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              	 To be used with JAX-RPC based runtime only.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="handler-chains"
>+                     type="javaee:handler-chainsType"
>+                     minOccurs="0"
>+                     maxOccurs="1">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              	 To be used with JAX-WS based runtime only.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+      </xsd:choice>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="service-impl-beanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The service-impl-bean element defines the web service implementation.
>+        A service implementation can be an EJB bean class or JAX-RPC web
>+        component.  Existing EJB implementations are exposed as a web service
>+        using an ejb-link.
>+        
>+        Used in: port-component
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:choice>
>+      <xsd:element name="ejb-link"
>+                   type="javaee:ejb-linkType"/>
>+      <xsd:element name="servlet-link"
>+                   type="javaee:servlet-linkType"/>
>+    </xsd:choice>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="servlet-linkType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The servlet-link element is used in the service-impl-bean element
>+        to specify that a Service Implementation Bean is defined as a
>+        JAX-RPC Service Endpoint.
>+        
>+        The value of the servlet-link element must be the servlet-name of
>+        a JAX-RPC Service Endpoint in the same WAR file.
>+        
>+        Used in: service-impl-bean
>+        
>+        Example:
>+        	  <servlet-link>StockQuoteService</servlet-link>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="webservice-descriptionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The webservice-description element defines a WSDL document file
>+        and the set of Port components associated with the WSDL ports
>+        defined in the WSDL document.  There may be multiple
>+        webservice-descriptions defined within a module.
>+        
>+        All WSDL file ports must have a corresponding port-component element
>+        defined.
>+        
>+        Used in: webservices
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="display-name"
>+                   type="javaee:display-nameType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="icon"
>+                   type="javaee:iconType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="webservice-description-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The webservice-description-name identifies the collection of
>+            port-components associated with a WSDL file and JAX-RPC
>+            mapping. The name must be unique within the deployment descriptor.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="wsdl-file"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The wsdl-file element contains the name of a WSDL file in the
>+            module.  The file name is a relative path within the module.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="jaxrpc-mapping-file"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The jaxrpc-mapping-file element contains the name of a file that
>+            describes the JAX-RPC mapping between the Java interaces used by
>+            the application and the WSDL description in the wsdl-file.  The
>+            file name is a relative path within the module.
>+            
>+            This is not required when JAX-WS based runtime is used.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="port-component"
>+                   type="javaee:port-componentType"
>+                   minOccurs="1"
>+                   maxOccurs="unbounded">
>+        <xsd:key name="port-component_handler-name-key">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              Defines the name of the handler. The name must be unique
>+              within the module.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:handler"/>
>+          <xsd:field xpath="javaee:handler-name"/>
>+        </xsd:key>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="webservicesType">
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="webservice-description"
>+                   type="javaee:webservice-descriptionType"
>+                   minOccurs="1"
>+                   maxOccurs="unbounded">
>+        <xsd:key name="port-component-name-key">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+              <![CDATA[[
>+              	The port-component-name element specifies a port
>+              	component's name.  This name is assigned by the module
>+              	producer to name the service implementation bean in the
>+              	module's deployment descriptor. The name must be unique
>+              	among the port component names defined in the same module.
>+              
>+              	Used in: port-component
>+              
>+              	Example:
>+              		<port-component-name>EmployeeService
>+              		</port-component-name>
>+              
>+              	
>+              
>+              ]]>
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:port-component"/>
>+          <xsd:field xpath="javaee:port-component-name"/>
>+        </xsd:key>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="version"
>+                   type="javaee:dewey-versionType"
>+                   fixed="1.3"
>+                   use="required">
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The required value for the version is 1.3.
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+    </xsd:attribute>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/jsp_2_2.xsd
>===================================================================
>RCS file: dtdsAndSchemas/jsp_2_2.xsd
>diff -N dtdsAndSchemas/jsp_2_2.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/jsp_2_2.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,389 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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.2">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      This is the XML Schema for the JSP 2.2 deployment descriptor
>+      types.  The JSP 2.2 schema contains all the special
>+      structures and datatypes that are necessary to use JSP files
>+      from a web application. 
>+      
>+      The contents of this schema is used by the web-common_3_0.xsd 
>+      file to define JSP specific content. 
>+      
>+    </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_6.xsd"/>
>+
>+
>+
>+
>+  <xsd:complexType name="jsp-configType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The jsp-configType is used to provide global configuration
>+        information for the JSP files in a web application. It has
>+        two subelements, taglib and jsp-property-group.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="taglib"
>+                   type="javaee:taglibType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="jsp-property-group"
>+                   type="javaee:jsp-property-groupType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="jsp-fileType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The jsp-file element contains the full path to a JSP file
>+        within the web application beginning with a `/'.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:pathType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="jsp-property-groupType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The jsp-property-groupType is used to group a number of
>+        files so they can be given global property information.
>+        All files so described are deemed to be JSP files.  The
>+        following additional properties can be described:
>+        
>+        - Control whether EL is ignored.
>+        - Control whether scripting elements are invalid.
>+        - Indicate pageEncoding information.
>+        - Indicate that a resource is a JSP document (XML).
>+        - Prelude and Coda automatic includes.
>+        - Control whether the character sequence #{ is allowed
>+        when used as a String literal.
>+        - Control whether template text containing only
>+        whitespaces must be removed from the response output.
>+        - Indicate the default contentType information.
>+        - Indicate the default buffering model for JspWriter
>+        - Control whether error should be raised for the use of
>+        undeclared namespaces in a JSP page.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="url-pattern"
>+                   type="javaee:url-patternType"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="el-ignored"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Can be used to easily set the isELIgnored
>+            property of a group of JSP pages.  By default, the
>+            EL evaluation is enabled for Web Applications using
>+            a Servlet 2.4 or greater web.xml, and disabled
>+            otherwise.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="page-encoding"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The valid values of page-encoding are those of the
>+            pageEncoding page directive.  It is a
>+            translation-time error to name different encodings
>+            in the pageEncoding attribute of the page directive
>+            of a JSP page and in a JSP configuration element
>+            matching the page.  It is also a translation-time
>+            error to name different encodings in the prolog
>+            or text declaration of a document in XML syntax and
>+            in a JSP configuration element matching the document.
>+            It is legal to name the same encoding through
>+            mulitple mechanisms.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="scripting-invalid"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Can be used to easily disable scripting in a
>+            group of JSP pages.  By default, scripting is
>+            enabled.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="is-xml"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            If true, denotes that the group of resources
>+            that match the URL pattern are JSP documents,
>+            and thus must be interpreted as XML documents.
>+            If false, the resources are assumed to not
>+            be JSP documents, unless there is another
>+            property group that indicates otherwise.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="include-prelude"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The include-prelude element is a context-relative
>+            path that must correspond to an element in the
>+            Web Application.  When the element is present,
>+            the given path will be automatically included (as
>+            in an include directive) at the beginning of each
>+            JSP page in this jsp-property-group.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="include-coda"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The include-coda element is a context-relative
>+            path that must correspond to an element in the
>+            Web Application.  When the element is present,
>+            the given path will be automatically included (as
>+            in an include directive) at the end of each
>+            JSP page in this jsp-property-group.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="deferred-syntax-allowed-as-literal"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The character sequence #{ is reserved for EL expressions.
>+            Consequently, a translation error occurs if the #{
>+            character sequence is used as a String literal, unless
>+            this element is enabled (true). Disabled (false) by
>+            default.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="trim-directive-whitespaces"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Indicates that template text containing only whitespaces
>+            must be removed from the response output. It has no
>+            effect on JSP documents (XML syntax). Disabled (false)
>+            by default.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="default-content-type"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The valid values of default-content-type are those of the
>+            contentType page directive.  It specifies the default
>+            response contentType if the page directive does not include
>+            a contentType attribute.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="buffer"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The valid values of buffer are those of the
>+            buffer page directive.  It specifies if buffering should be
>+            used for the output to response, and if so, the size of the
>+            buffer to use.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="error-on-undeclared-namespace"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The default behavior when a tag with unknown namespace is used
>+            in a JSP page (regular syntax) is to silently ignore it.  If
>+            set to true, then an error must be raised during the translation
>+            time when an undeclared tag is used in a JSP page.  Disabled
>+            (false) by default.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="taglibType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The taglibType defines the syntax for declaring in
>+        the deployment descriptor that a tag library is
>+        available to the application.  This can be done
>+        to override implicit map entries from TLD files and
>+        from the container.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="taglib-uri"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            A taglib-uri element describes a URI identifying a
>+            tag library used in the web application.  The body
>+            of the taglib-uri element may be either an
>+            absolute URI specification, or a relative URI.
>+            There should be no entries in web.xml with the
>+            same taglib-uri value.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="taglib-location"
>+                   type="javaee:pathType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            the taglib-location element contains the location
>+            (as a resource relative to the root of the web
>+            application) where to find the Tag Library
>+            Description file for the tag library.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/web-app_3_0.xsd
>===================================================================
>RCS file: dtdsAndSchemas/web-app_3_0.xsd
>diff -N dtdsAndSchemas/web-app_3_0.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/web-app_3_0.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,272 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="3.0">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the XML Schema for the Servlet 3.0 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="3.0"> 
>+      ...
>+      </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_3_0.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="web-common_3_0.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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-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-common-role-name-references"
>+                refer="javaee:web-common-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:schema>
>Index: dtdsAndSchemas/javaee_6.xsd
>===================================================================
>RCS file: dtdsAndSchemas/javaee_6.xsd
>diff -N dtdsAndSchemas/javaee_6.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/javaee_6.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,2422 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<xsd:schema 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="6">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      The following definitions that appear in the common
>+      shareable schema(s) of Java EE deployment descriptors should be
>+      interpreted with respect to the context they are included:
>+      
>+      Deployment Component may indicate one of the following:
>+      java ee application;
>+      application client;
>+      web application;
>+      enterprise bean;
>+      resource adapter; 
>+      
>+      Deployment File may indicate one of the following:
>+      ear file;
>+      war file;
>+      jar file;
>+      rar file;
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
>+              schemaLocation="http://www.w3.org/2001/xml.xsd"/>
>+
>+  <xsd:include schemaLocation="javaee_web_services_client_1_3.xsd"/>
>+
>+  <xsd:group name="descriptionGroup">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This group keeps the usage of the contained description related
>+        elements consistent across Java EE deployment descriptors.
>+        
>+        All elements may occur multiple times with different languages,
>+        to support localization of the content.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="display-name"
>+                   type="javaee:display-nameType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="icon"
>+                   type="javaee:iconType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+  </xsd:group>
>+
>+  <xsd:group name="jndiEnvironmentRefsGroup">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This group keeps the usage of the contained JNDI environment
>+        reference elements consistent across Java EE deployment descriptors.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="env-entry"
>+                   type="javaee:env-entryType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-ref"
>+                   type="javaee:ejb-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-local-ref"
>+                   type="javaee:ejb-local-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:group ref="javaee:service-refGroup"/>
>+      <xsd:element name="resource-ref"
>+                   type="javaee:resource-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="resource-env-ref"
>+                   type="javaee:resource-env-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination-ref"
>+                   type="javaee:message-destination-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-context-ref"
>+                   type="javaee:persistence-context-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-unit-ref"
>+                   type="javaee:persistence-unit-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="post-construct"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="pre-destroy"
>+                   type="javaee:lifecycle-callbackType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="data-source"
>+                   type="javaee:data-sourceType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+  </xsd:group>
>+
>+  <xsd:group name="resourceGroup">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This group collects elements that are common to most
>+        JNDI resource elements.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:resourceBaseGroup"/>
>+      <xsd:element name="lookup-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The JNDI name to be looked up to resolve a resource reference.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+  </xsd:group>
>+
>+  <xsd:group name="resourceBaseGroup">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This group collects elements that are common to all the
>+        JNDI resource elements. It does not include the lookup-name
>+        element, that is only applicable to some resource elements.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="mapped-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            A product specific name that this resource should be
>+            mapped to.  The name of this resource, as defined by the
>+            resource's name element or defaulted, is a name that is
>+            local to the application component using the resource.
>+            (It's a name in the JNDI java:comp/env namespace.)  Many
>+            application servers provide a way to map these local
>+            names to names of resources known to the application
>+            server.  This mapped name is often a global JNDI name,
>+            but may be a name of any form.
>+            
>+            Application servers are not required to support any
>+            particular form or type of mapped name, nor the ability
>+            to use mapped names.  The mapped name is
>+            product-dependent and often installation-dependent.  No
>+            use of a mapped name is portable.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="injection-target"
>+                   type="javaee:injection-targetType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+  </xsd:group>
>+
>+
>+
>+
>+  <xsd:complexType name="data-sourceType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Configuration of a DataSource.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Description of this DataSource.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="name"
>+                   type="javaee:jndi-nameType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The name element specifies the JNDI name of the
>+            data source being defined.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="class-name"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            DataSource, XADataSource or ConnectionPoolDataSource
>+            implementation class.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="server-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Database server name.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="port-number"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Port number where a server is listening for requests.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="database-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Name of a database on a server.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="url"
>+                   type="javaee:jdbc-urlType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            A JDBC URL. If the <code>url</code> property is specified
>+            along with other standard <code>DataSource</code> properties
>+            such as <code>serverName</code>, <code>databaseName</code>
>+            and <code>portNumber</code>, the more specific properties will
>+            take precedence and <code>url</code> will be ignored.
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="user"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            User name to use for connection authentication.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="password"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Password to use for connection authentication.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="property"
>+                   type="javaee:propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            JDBC DataSource property.  This may be a vendor-specific
>+            property or a less commonly used DataSource property.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="login-timeout"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Sets the maximum time in seconds that this data source
>+            will wait while attempting to connect to a database.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="transactional"
>+                   type="javaee:xsdBooleanType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Set to false if connections should not participate in
>+            transactions.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="isolation-level"
>+                   type="javaee:isolation-levelType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Isolation level for connections.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="initial-pool-size"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Number of connections that should be created when a
>+            connection pool is initialized.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-pool-size"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Maximum number of connections that should be concurrently
>+            allocated for a connection pool.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="min-pool-size"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Minimum number of connections that should be concurrently
>+            allocated for a connection pool.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-idle-time"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The number of seconds that a physical connection should
>+            remain unused in the pool before the connection is
>+            closed for a connection pool.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-statements"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The total number of statements that a connection pool
>+            should keep open.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="descriptionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The description type is used by a description element to
>+        provide text describing the parent element.  The elements
>+        that use this type should include any information that the
>+        Deployment Component's Deployment File file producer wants
>+        to provide to the consumer of the Deployment Component's
>+        Deployment File (i.e., to the Deployer). Typically, the
>+        tools used by such a Deployment File consumer will display
>+        the description when processing the parent element that
>+        contains the description.
>+        
>+        The lang attribute defines the language that the
>+        description is provided in. The default value is "en" (English). 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:xsdStringType">
>+        <xsd:attribute ref="xml:lang"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+  <xsd:simpleType name="dewey-versionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type defines a dewey decimal that is used
>+        to describe versions of documents. 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:token">
>+      <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+
>+
>+
>+  <xsd:complexType name="display-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The display-name type contains a short name that is intended
>+        to be displayed by tools. It is used by display-name
>+        elements.  The display name need not be unique.
>+        
>+        Example: 
>+        
>+        ...
>+        <display-name xml:lang="en">
>+        Employee Self Service
>+        </display-name>
>+        
>+        The value of the xml:lang attribute is "en" (English) by default. 
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:string">
>+        <xsd:attribute ref="xml:lang"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-linkType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The ejb-linkType is used by ejb-link
>+        elements in the ejb-ref or ejb-local-ref elements to specify
>+        that an EJB reference is linked to enterprise bean.
>+        
>+        The value of the ejb-link element must be the ejb-name of an
>+        enterprise bean in the same ejb-jar file or in another ejb-jar
>+        file in the same Java EE application unit. 
>+        
>+        Alternatively, the name in the ejb-link element may be
>+        composed of a path name specifying the ejb-jar containing the
>+        referenced enterprise bean with the ejb-name of the target
>+        bean appended and separated from the path name by "#".  The
>+        path name is relative to the Deployment File containing
>+        Deployment Component that is referencing the enterprise
>+        bean.  This allows multiple enterprise beans with the same
>+        ejb-name to be uniquely identified.
>+        
>+        Examples:
>+        
>+        <ejb-link>EmployeeRecord</ejb-link>
>+        
>+        <ejb-link>../products/product.jar#ProductEJB</ejb-link>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-local-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The ejb-local-refType is used by ejb-local-ref elements for
>+        the declaration of a reference to an enterprise bean's local
>+        home or to the local business interface of a 3.0 bean.
>+        The declaration consists of:
>+        
>+        - an optional description
>+        - the EJB reference name used in the code of the Deployment 
>+        Component that's referencing the enterprise bean.
>+        - the optional expected type of the referenced enterprise bean
>+        - the optional expected local interface of the referenced 
>+        enterprise bean or the local business interface of the 
>+        referenced enterprise bean.
>+        - the optional expected local home interface of the referenced 
>+        enterprise bean. Not applicable if this ejb-local-ref refers
>+        to the local business interface of a 3.0 bean.
>+        - optional ejb-link information, used to specify the 
>+        referenced enterprise bean
>+        - optional elements to define injection of the named enterprise  
>+        bean into a component field or property.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-ref-name"
>+                   type="javaee:ejb-ref-nameType"/>
>+      <xsd:element name="ejb-ref-type"
>+                   type="javaee:ejb-ref-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local-home"
>+                   type="javaee:local-homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="local"
>+                   type="javaee:localType"
>+                   minOccurs="0"/>
>+      <xsd:element name="ejb-link"
>+                   type="javaee:ejb-linkType"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-ref-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The ejb-ref-name element contains the name of an EJB
>+        reference. The EJB reference is an entry in the
>+        Deployment Component's environment and is relative to the
>+        java:comp/env context.  The name must be unique within the
>+        Deployment Component.
>+        
>+        It is recommended that name is prefixed with "ejb/".
>+        
>+        Example:
>+        
>+        <ejb-ref-name>ejb/Payroll</ejb-ref-name>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:jndi-nameType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The ejb-refType is used by ejb-ref elements for the
>+        declaration of a reference to an enterprise bean's home or
>+        to the remote business interface of a 3.0 bean.  
>+        The declaration consists of:
>+        
>+        - an optional description
>+        - the EJB reference name used in the code of
>+        the Deployment Component that's referencing the enterprise
>+        bean. 
>+        - the optional expected type of the referenced enterprise bean
>+        - the optional remote interface of the referenced enterprise bean
>+        or the remote business interface of the referenced enterprise 
>+        bean
>+        - the optional expected home interface of the referenced 
>+        enterprise bean.  Not applicable if this ejb-ref
>+        refers to the remote business interface of a 3.0 bean.
>+        - optional ejb-link information, used to specify the
>+        referenced enterprise bean
>+        - optional elements to define injection of the named enterprise
>+        bean into a component field or property
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="ejb-ref-name"
>+                   type="javaee:ejb-ref-nameType"/>
>+      <xsd:element name="ejb-ref-type"
>+                   type="javaee:ejb-ref-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="home"
>+                   type="javaee:homeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="remote"
>+                   type="javaee:remoteType"
>+                   minOccurs="0"/>
>+      <xsd:element name="ejb-link"
>+                   type="javaee:ejb-linkType"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ejb-ref-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The ejb-ref-typeType contains the expected type of the
>+        referenced enterprise bean.
>+        
>+        The ejb-ref-type designates a value
>+        that must be one of the following:
>+        
>+        Entity
>+        Session
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Entity"/>
>+        <xsd:enumeration value="Session"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="emptyType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type is used to designate an empty
>+        element when used. 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="env-entryType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The env-entryType is used to declare an application's
>+        environment entry. The declaration consists of an optional
>+        description, the name of the environment entry, a type
>+        (optional if the value is injected, otherwise required), and
>+        an optional value.
>+        
>+        It also includes optional elements to define injection of
>+        the named resource into fields or JavaBeans properties.
>+        
>+        If a value is not specified and injection is requested,
>+        no injection will occur and no entry of the specified name
>+        will be created.  This allows an initial value to be
>+        specified in the source code without being incorrectly
>+        changed when no override has been specified.
>+        
>+        If a value is not specified and no injection is requested,
>+        a value must be supplied during deployment. 
>+        
>+        This type is used by env-entry elements.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="env-entry-name"
>+                   type="javaee:jndi-nameType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The env-entry-name element contains the name of a
>+            Deployment Component's environment entry.  The name
>+            is a JNDI name relative to the java:comp/env
>+            context.  The name must be unique within a 
>+            Deployment Component. The uniqueness
>+            constraints must be defined within the declared
>+            context.
>+            
>+            Example:
>+            
>+            <env-entry-name>minAmount</env-entry-name>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="env-entry-type"
>+                   type="javaee:env-entry-type-valuesType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The env-entry-type element contains the Java language
>+            type of the environment entry.  If an injection target
>+            is specified for the environment entry, the type may
>+            be omitted, or must match the type of the injection
>+            target.  If no injection target is specified, the type
>+            is required.
>+            
>+            Example:
>+            
>+            <env-entry-type>java.lang.Integer</env-entry-type>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="env-entry-value"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The env-entry-value designates the value of a
>+            Deployment Component's environment entry. The value
>+            must be a String that is valid for the
>+            constructor of the specified type that takes a
>+            single String parameter, or for java.lang.Character,
>+            a single character.
>+            
>+            Example:
>+            
>+            <env-entry-value>100.00</env-entry-value>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="env-entry-type-valuesType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        This type contains the fully-qualified Java type of the
>+        environment entry value that is expected by the
>+        application's code.
>+        
>+        The following are the legal values of env-entry-type-valuesType:
>+        
>+        java.lang.Boolean
>+        java.lang.Byte
>+        java.lang.Character
>+        java.lang.String
>+        java.lang.Short
>+        java.lang.Integer
>+        java.lang.Long
>+        java.lang.Float
>+        java.lang.Double
>+        		  java.lang.Class
>+        		  any enumeration type (i.e. a subclass of java.lang.Enum)
>+        
>+        Examples:
>+        
>+        <env-entry-type>java.lang.Boolean</env-entry-type>
>+        <env-entry-type>java.lang.Class</env-entry-type>
>+        <env-entry-type>com.example.Color</env-entry-type>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="fully-qualified-classType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The elements that use this type designate the name of a
>+        Java class or interface.  The name is in the form of a
>+        "binary name", as defined in the JLS.  This is the form
>+        of name used in Class.forName().  Tools that need the
>+        canonical name (the name used in source code) will need
>+        to convert this binary name to the canonical name.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="generic-booleanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type defines four different values which can designate
>+        boolean values. This includes values yes and no which are 
>+        not designated by xsd:boolean
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="true"/>
>+        <xsd:enumeration value="false"/>
>+        <xsd:enumeration value="yes"/>
>+        <xsd:enumeration value="no"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="iconType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The icon type contains small-icon and large-icon elements
>+        that specify the file names for small and large GIF, JPEG,
>+        or PNG icon images used to represent the parent element in a
>+        GUI tool. 
>+        
>+        The xml:lang attribute defines the language that the
>+        icon file names are provided in. Its value is "en" (English)
>+        by default. 
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="small-icon"
>+                   type="javaee:pathType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The small-icon element contains the name of a file
>+            containing a small (16 x 16) icon image. The file
>+            name is a relative path within the Deployment
>+            Component's Deployment File.
>+            
>+            The image may be in the GIF, JPEG, or PNG format.
>+            The icon can be used by tools.
>+            
>+            Example:
>+            
>+            <small-icon>employee-service-icon16x16.jpg</small-icon>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="large-icon"
>+                   type="javaee:pathType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+            <![CDATA[[
>+            The large-icon element contains the name of a file
>+            containing a large
>+            (32 x 32) icon image. The file name is a relative 
>+            path within the Deployment Component's Deployment
>+            File.
>+            
>+            The image may be in the GIF, JPEG, or PNG format.
>+            The icon can be used by tools.
>+            
>+            Example:
>+            
>+            <large-icon>employee-service-icon32x32.jpg</large-icon>
>+            
>+            ]]>
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute ref="xml:lang"/>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="injection-targetType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        An injection target specifies a class and a name within
>+        that class into which a resource should be injected.
>+        
>+        The injection target class specifies the fully qualified
>+        class name that is the target of the injection.  The
>+        Java EE specifications describe which classes can be an
>+        injection target.
>+        
>+        The injection target name specifies the target within
>+        the specified class.  The target is first looked for as a
>+        JavaBeans property name.  If not found, the target is
>+        looked for as a field name.
>+        
>+        The specified resource will be injected into the target
>+        during initialization of the class by either calling the
>+        set method for the target property or by setting a value
>+        into the named field.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="injection-target-class"
>+                   type="javaee:fully-qualified-classType"/>
>+      <xsd:element name="injection-target-name"
>+                   type="javaee:java-identifierType"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+  <xsd:simpleType name="isolation-levelType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        	The following transaction isolation levels are allowed
>+        	(see documentation for the java.sql.Connection interface):
>+        TRANSACTION_READ_UNCOMMITTED
>+        TRANSACTION_READ_COMMITTED
>+        TRANSACTION_REPEATABLE_READ
>+        TRANSACTION_SERIALIZABLE
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:string">
>+      <xsd:enumeration value="TRANSACTION_READ_UNCOMMITTED"/>
>+      <xsd:enumeration value="TRANSACTION_READ_COMMITTED"/>
>+      <xsd:enumeration value="TRANSACTION_REPEATABLE_READ"/>
>+      <xsd:enumeration value="TRANSACTION_SERIALIZABLE"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+
>+
>+
>+  <xsd:complexType name="java-identifierType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The java-identifierType defines a Java identifier.
>+        The users of this type should further verify that 
>+        the content does not contain Java reserved keywords.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="java-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This is a generic type that designates a Java primitive
>+        type or a fully qualified name of a Java interface/type,
>+        or an array of such types.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:pattern value="[^\p{Z}]*"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="jdbc-urlType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The jdbc-urlType contains the url pattern of the mapping.
>+        It must follow the rules specified in Section 9.3 of the
>+        JDBC Specification where the format is:
>+        
>+        jdbc:<subprotocol>:<subname>
>+        
>+        Example:
>+        
>+        <url>jdbc:mysql://localhost:3307/testdb</url>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:pattern value="jdbc:(.*):(.*)"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="jndi-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The jndi-nameType type designates a JNDI name in the
>+        Deployment Component's environment and is relative to the
>+        java:comp/env context.  A JNDI name must be unique within the
>+        Deployment Component.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="homeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The homeType defines the fully-qualified name of
>+        an enterprise bean's home interface. 
>+        
>+        Example:
>+        
>+        <home>com.aardvark.payroll.PayrollHome</home>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="lifecycle-callbackType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The lifecycle-callback type specifies a method on a
>+        class to be called when a lifecycle event occurs.
>+        Note that each class may have only one lifecycle callback
>+        method for any given event and that the method may not
>+        be overloaded.
>+        
>+        If the lifefycle-callback-class element is missing then
>+        the class defining the callback is assumed to be the
>+        component class in scope at the place in the descriptor
>+        in which the callback definition appears.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="lifecycle-callback-class"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"/>
>+      <xsd:element name="lifecycle-callback-method"
>+                   type="javaee:java-identifierType"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="listenerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The listenerType indicates the deployment properties for a web
>+        application listener bean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="listener-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The listener-class element declares a class in the
>+            application must be registered as a web
>+            application listener bean. The value is the fully
>+            qualified classname of the listener class.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="localType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The localType defines the fully-qualified name of an
>+        enterprise bean's local interface.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="local-homeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The local-homeType defines the fully-qualified
>+        name of an enterprise bean's local home interface.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="param-valueType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type is a general type that can be used to declare
>+        parameter/value lists.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="param-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The param-name element contains the name of a
>+            parameter.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="param-value"
>+                   type="javaee:xsdStringType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The param-value element contains the value of a
>+            parameter.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="pathType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The elements that use this type designate either a relative
>+        path or an absolute path starting with a "/".
>+        
>+        In elements that specify a pathname to a file within the
>+        same Deployment File, relative filenames (i.e., those not
>+        starting with "/") are considered relative to the root of
>+        the Deployment File's namespace.  Absolute filenames (i.e.,
>+        those starting with "/") also specify names in the root of
>+        the Deployment 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:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="persistence-context-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The persistence-context-ref element contains a declaration
>+        of Deployment Component's reference to a persistence context
>+        associated within a Deployment Component's
>+        environment. It consists of:
>+        
>+        - an optional description
>+        - the persistence context reference name
>+        - an optional persistence unit name.  If not specified,
>+        the default persistence unit is assumed.
>+        - an optional specification as to whether
>+        the persistence context type is Transaction or
>+        Extended.  If not specified, Transaction is assumed.
>+        - an optional list of persistence properties
>+        - optional injection targets
>+        
>+        Examples:
>+        
>+        <persistence-context-ref>
>+        <persistence-context-ref-name>myPersistenceContext
>+        </persistence-context-ref-name>
>+        </persistence-context-ref>
>+        
>+        <persistence-context-ref>
>+        <persistence-context-ref-name>myPersistenceContext
>+        </persistence-context-ref-name>
>+        <persistence-unit-name>PersistenceUnit1
>+        </persistence-unit-name>
>+        <persistence-context-type>Extended</persistence-context-type>
>+        </persistence-context-ref>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-context-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The persistence-context-ref-name element specifies
>+            the name of a persistence context reference; its
>+            value is the environment entry name used in
>+            Deployment Component code.  The name is a JNDI name
>+            relative to the java:comp/env context.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="persistence-unit-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The Application Assembler(or BeanProvider) may use the
>+            following syntax to avoid the need to rename persistence
>+            units to have unique names within a Java EE application.
>+            
>+            The Application Assembler specifies the pathname of the
>+            root of the persistence.xml file for the referenced
>+            persistence unit and appends the name of the persistence
>+            unit separated from the pathname by #. The pathname is
>+            relative to the referencing application component jar file. 
>+            In this manner, multiple persistence units with the same
>+            persistence unit name may be uniquely identified when the 
>+            Application Assembler cannot change persistence unit names.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="persistence-context-type"
>+                   type="javaee:persistence-context-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="persistence-property"
>+                   type="javaee:propertyType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Used to specify properties for the container or persistence
>+            provider.  Vendor-specific properties may be included in
>+            the set of properties.  Properties that are not recognized
>+            by a vendor must be ignored.  Entries that make use of the 
>+            namespace javax.persistence and its subnamespaces must not
>+            be used for vendor-specific properties.  The namespace
>+            javax.persistence is reserved for use by the specification.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:resourceBaseGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="persistence-context-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The persistence-context-typeType specifies the transactional
>+        nature of a persistence context reference.  
>+        
>+        The value of the persistence-context-type element must be
>+        one of the following:
>+        Transaction
>+        Extended
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Transaction"/>
>+        <xsd:enumeration value="Extended"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="propertyType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Specifies a name/value pair.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="name"
>+                   type="javaee:xsdStringType">
>+      </xsd:element>
>+      <xsd:element name="value"
>+                   type="javaee:xsdStringType">
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="persistence-unit-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The persistence-unit-ref element contains a declaration
>+        of Deployment Component's reference to a persistence unit
>+        associated within a Deployment Component's
>+        environment. It consists of:
>+        
>+        - an optional description
>+        - the persistence unit reference name
>+        - an optional persistence unit name.  If not specified,
>+        the default persistence unit is assumed.
>+        - optional injection targets
>+        
>+        Examples:
>+        
>+        <persistence-unit-ref>
>+        <persistence-unit-ref-name>myPersistenceUnit
>+        </persistence-unit-ref-name>
>+        </persistence-unit-ref>
>+        
>+        <persistence-unit-ref>
>+        <persistence-unit-ref-name>myPersistenceUnit
>+        </persistence-unit-ref-name>
>+        <persistence-unit-name>PersistenceUnit1
>+        </persistence-unit-name>
>+        </persistence-unit-ref>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="persistence-unit-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The persistence-unit-ref-name element specifies
>+            the name of a persistence unit reference; its
>+            value is the environment entry name used in
>+            Deployment Component code.  The name is a JNDI name
>+            relative to the java:comp/env context.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="persistence-unit-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The Application Assembler(or BeanProvider) may use the
>+            following syntax to avoid the need to rename persistence
>+            units to have unique names within a Java EE application.
>+            
>+            The Application Assembler specifies the pathname of the
>+            root of the persistence.xml file for the referenced
>+            persistence unit and appends the name of the persistence
>+            unit separated from the pathname by #. The pathname is
>+            relative to the referencing application component jar file. 
>+            In this manner, multiple persistence units with the same
>+            persistence unit name may be uniquely identified when the 
>+            Application Assembler cannot change persistence unit names.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:resourceBaseGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="remoteType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The remote element contains the fully-qualified name
>+        of the enterprise bean's remote interface.
>+        
>+        Example:
>+        
>+        <remote>com.wombat.empl.EmployeeService</remote>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="resource-env-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The resource-env-refType is used to define
>+        resource-env-ref elements.  It contains a declaration of a
>+        Deployment Component's reference to an administered object
>+        associated with a resource in the Deployment Component's
>+        environment.  It consists of an optional description, the
>+        resource environment reference name, and an optional
>+        indication of the resource environment reference type
>+        expected by the Deployment Component code.
>+        
>+        It also includes optional elements to define injection of
>+        the named resource into fields or JavaBeans properties.
>+        
>+        The resource environment type must be supplied unless an
>+        injection target is specified, in which case the type
>+        of the target is used.  If both are specified, the type
>+        must be assignment compatible with the type of the injection
>+        target.
>+        
>+        Example:
>+        
>+        <resource-env-ref>
>+        <resource-env-ref-name>jms/StockQueue
>+        </resource-env-ref-name>
>+        <resource-env-ref-type>javax.jms.Queue
>+        </resource-env-ref-type>
>+        </resource-env-ref>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="resource-env-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <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 Deployment Component code.  The name is a JNDI 
>+            name relative to the java:comp/env context and must 
>+            be unique within a Deployment Component.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="resource-env-ref-type"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The resource-env-ref-type element specifies the type
>+            of a resource environment reference.  It is the
>+            fully qualified name of a Java language class or
>+            interface.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="resource-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The resource-refType contains a declaration of a
>+        Deployment Component's reference to an external resource. It
>+        consists of an optional description, the resource manager
>+        connection factory reference name, an optional indication of
>+        the resource manager connection factory type expected by the
>+        Deployment Component code, an optional type of authentication
>+        (Application or Container), and an optional specification of
>+        the shareability of connections obtained from the resource
>+        (Shareable or Unshareable).
>+        
>+        It also includes optional elements to define injection of
>+        the named resource into fields or JavaBeans properties.
>+        
>+        The connection factory type must be supplied unless an
>+        injection target is specified, in which case the type
>+        of the target is used.  If both are specified, the type
>+        must be assignment compatible with the type of the injection
>+        target.
>+        
>+        Example:
>+        
>+        <resource-ref>
>+        <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
>+        <res-type>javax.sql.DataSource</res-type>
>+        <res-auth>Container</res-auth>
>+        <res-sharing-scope>Shareable</res-sharing-scope>
>+        </resource-ref>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="res-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <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 Deployment File. 
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="res-type"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The res-type element specifies the type of the data
>+            source. The type is specified by the fully qualified
>+            Java language class or interface
>+            expected to be implemented by the data source.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="res-auth"
>+                   type="javaee:res-authType"
>+                   minOccurs="0"/>
>+      <xsd:element name="res-sharing-scope"
>+                   type="javaee:res-sharing-scopeType"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="res-authType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The res-authType specifies whether the Deployment Component
>+        code signs on programmatically to the resource manager, or
>+        whether the Container will sign on to the resource manager
>+        on behalf of the Deployment Component. In the latter case,
>+        the Container uses information that is supplied by the
>+        Deployer.
>+        
>+        The value must be one of the two following:
>+        
>+        Application
>+        Container
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Application"/>
>+        <xsd:enumeration value="Container"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="res-sharing-scopeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The res-sharing-scope type specifies whether connections
>+        obtained through the given resource manager connection
>+        factory reference can be shared. The value, if specified,
>+        must be one of the two following:
>+        
>+        Shareable
>+        Unshareable
>+        
>+        The default value is Shareable.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Shareable"/>
>+        <xsd:enumeration value="Unshareable"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="run-asType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The run-asType specifies the run-as identity to be
>+        used for the execution of a component. It contains an 
>+        optional description, and the name of a security role.
>+        
>+      </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"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="role-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The role-nameType designates the name of a security role.
>+        
>+        The name must conform to the lexical rules for a token.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="security-roleType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The security-roleType contains the definition of a security
>+        role. The definition consists of an optional description of
>+        the security role, and the security role name.
>+        
>+        Example:
>+        
>+        <security-role>
>+        <description>
>+        This role includes all employees who are authorized
>+        to access the employee service application.
>+        </description>
>+        <role-name>employee</role-name>
>+        </security-role>
>+        
>+        ]]>
>+      </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"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="security-role-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The security-role-refType contains the declaration of a
>+        security role reference in a component's or a
>+        Deployment Component's code. The declaration consists of an
>+        optional description, the security role name used in the
>+        code, and an optional link to a security role. If the
>+        security role is not specified, the Deployer must choose an
>+        appropriate security role.
>+        
>+      </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">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The value of the role-name element must be the String used
>+            as the parameter to the 
>+            EJBContext.isCallerInRole(String roleName) method or the
>+            HttpServletRequest.isUserInRole(String role) method.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="role-link"
>+                   type="javaee:role-nameType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The role-link element is a reference to a defined
>+            security role. The role-link element must contain
>+            the name of one of the security roles defined in the
>+            security-role elements.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdQNameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:QName.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:QName">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdBooleanType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:boolean.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:boolean">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdNMTOKENType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:NMTOKEN.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:NMTOKEN">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdAnyURIType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:anyURI.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:anyURI">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdIntegerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:integer.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:integer">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdPositiveIntegerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:positiveInteger.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:positiveInteger">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdNonNegativeIntegerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:nonNegativeInteger.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:nonNegativeInteger">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="xsdStringType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type adds an "id" attribute to xsd:string.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:string">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="string">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This is a special string datatype that is defined by Java EE as
>+        a base type for defining collapsed strings. When schemas
>+        require trailing/leading space elimination as well as
>+        collapsing the existing whitespace, this base type may be
>+        used.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:token">
>+        <xsd:attribute name="id"
>+                       type="xsd:ID"/>
>+      </xsd:extension>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="true-falseType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This simple type designates a boolean with only two
>+        permissible values
>+        
>+        - true
>+        - false
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:xsdBooleanType">
>+        <xsd:pattern value="(true|false)"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="url-patternType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The url-patternType contains the url pattern of the mapping.
>+        It must follow the rules specified in Section 11.2 of the
>+        Servlet API Specification. This pattern is assumed to be in
>+        URL-decoded form and must not contain CR(#xD) or LF(#xA).
>+        If it contains those characters, the container must inform
>+        the developer with a descriptive error message.
>+        The container must preserve all characters including whitespaces.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="xsd:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-destinationType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The message-destinationType specifies a message
>+        destination. The logical destination described by this
>+        element is mapped to a physical destination by the Deployer.
>+        
>+        The message destination element contains: 
>+        
>+        - an optional description
>+        - an optional display-name
>+        - an optional icon
>+        - a message destination name which must be unique
>+        among message destination names within the same 
>+        Deployment File. 
>+        - an optional mapped name
>+        - an optional lookup name
>+        
>+        Example: 
>+        
>+        <message-destination>
>+        <message-destination-name>CorporateStocks
>+        </message-destination-name>
>+        </message-destination>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="message-destination-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The message-destination-name element specifies a
>+            name for a message destination.  This name must be
>+            unique among the names of message destinations
>+            within the Deployment File.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="mapped-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            A product specific name that this message destination
>+            should be mapped to.  Each message-destination-ref
>+            element that references this message destination will
>+            define a name in the namespace of the referencing
>+            component or in one of the other predefined namespaces. 
>+            Many application servers provide a way to map these
>+            local names to names of resources known to the
>+            application server.  This mapped name is often a global
>+            JNDI name, but may be a name of any form.  Each of the
>+            local names should be mapped to this same global name.
>+            
>+            Application servers are not required to support any
>+            particular form or type of mapped name, nor the ability
>+            to use mapped names.  The mapped name is
>+            product-dependent and often installation-dependent.  No
>+            use of a mapped name is portable.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="lookup-name"
>+                   type="javaee:xsdStringType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The JNDI name to be looked up to resolve the message destination.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-destination-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The message-destination-ref element contains a declaration
>+        of Deployment Component's reference to a message destination
>+        associated with a resource in Deployment Component's
>+        environment. It consists of:
>+        
>+        - an optional description
>+        - the message destination reference name
>+        - an optional message destination type
>+        - an optional specification as to whether
>+        the destination is used for 
>+        consuming or producing messages, or both.
>+        if not specified, "both" is assumed.
>+        - an optional link to the message destination
>+        - optional injection targets
>+        
>+        The message destination type must be supplied unless an
>+        injection target is specified, in which case the type
>+        of the target is used.  If both are specified, the type
>+        must be assignment compatible with the type of the injection
>+        target.
>+        
>+        Examples:
>+        
>+        <message-destination-ref>
>+        <message-destination-ref-name>jms/StockQueue
>+        </message-destination-ref-name>
>+        <message-destination-type>javax.jms.Queue
>+        </message-destination-type>
>+        <message-destination-usage>Consumes
>+        </message-destination-usage>
>+        <message-destination-link>CorporateStocks
>+        </message-destination-link>
>+        </message-destination-ref>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="description"
>+                   type="javaee:descriptionType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="message-destination-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <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
>+            Deployment Component code.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="message-destination-type"
>+                   type="javaee:message-destination-typeType"
>+                   minOccurs="0"/>
>+      <xsd:element name="message-destination-usage"
>+                   type="javaee:message-destination-usageType"
>+                   minOccurs="0"/>
>+      <xsd:element name="message-destination-link"
>+                   type="javaee:message-destination-linkType"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-destination-usageType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The message-destination-usageType specifies the use of the
>+        message destination indicated by the reference.  The value
>+        indicates whether messages are consumed from the message
>+        destination, produced for the destination, or both.  The
>+        Assembler makes use of this information in linking producers
>+        of a destination with its consumers.
>+        
>+        The value of the message-destination-usage element must be
>+        one of the following:
>+        Consumes
>+        Produces
>+        ConsumesProduces
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="Consumes"/>
>+        <xsd:enumeration value="Produces"/>
>+        <xsd:enumeration value="ConsumesProduces"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-destination-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+        <![CDATA[[
>+        The message-destination-typeType specifies the type of
>+        the destination. The type is specified by the Java interface
>+        expected to be implemented by the destination.
>+        
>+        Example: 
>+        
>+        <message-destination-type>javax.jms.Queue
>+        </message-destination-type>
>+        
>+        ]]>
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:fully-qualified-classType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="message-destination-linkType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The message-destination-linkType is used to link a message
>+        destination reference or message-driven bean to a message
>+        destination.
>+        
>+        The Assembler sets the value to reflect the flow of messages
>+        between producers and consumers in the application.
>+        
>+        The value must be the message-destination-name of a message
>+        destination in the same Deployment File or in another
>+        Deployment File in the same Java EE application unit.
>+        
>+        Alternatively, the value may be composed of a path name
>+        specifying a Deployment File containing the referenced
>+        message destination with the message-destination-name of the
>+        destination appended and separated from the path name by
>+        "#". The path name is relative to the Deployment File
>+        containing Deployment Component that is referencing the
>+        message destination.  This allows multiple message
>+        destinations with the same name to be uniquely identified.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/web-common_3_0.xsd
>===================================================================
>RCS file: dtdsAndSchemas/web-common_3_0.xsd
>diff -N dtdsAndSchemas/web-common_3_0.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/web-common_3_0.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,1575 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="3.0">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+      <![CDATA[[
>+      This is the common XML Schema for the Servlet 3.0 deployment descriptor.
>+      This file is in turn used by web.xml and web-fragment.xml
>+      web application's war file.  All Servlet deployment descriptors
>+      must indicate the web common 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="3.0"> 
>+      ...
>+      </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-common_3_0.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_6.xsd"/>
>+
>+  <xsd:include schemaLocation="jsp_2_2.xsd"/>
>+
>+  <xsd:group name="web-commonType">
>+    <xsd:choice>
>+      <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:group>
>+
>+  <xsd:attributeGroup name="web-common-attributes">
>+    <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:attributeGroup>
>+
>+
>+
>+
>+  <xsd:complexType name="web-appType">
>+    <xsd:choice minOccurs="0"
>+                maxOccurs="unbounded">
>+      <xsd:element name="module-name"
>+                   type="javaee:string"
>+                   minOccurs="0"/>
>+      <xsd:group ref="javaee:web-commonType"/>
>+      <xsd:element name="absolute-ordering"
>+                   type="javaee:absoluteOrderingType"/>
>+    </xsd:choice>
>+    <xsd:attributeGroup ref="javaee:web-common-attributes"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="web-fragmentType">
>+    <xsd:choice minOccurs="0"
>+                maxOccurs="unbounded">
>+      <xsd:element name="name"
>+                   type="javaee:java-identifierType"/>
>+      <xsd:group ref="javaee:web-commonType"/>
>+      <xsd:element name="ordering"
>+                   type="javaee:orderingType"/>
>+    </xsd:choice>
>+    <xsd:attributeGroup ref="javaee:web-common-attributes"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <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 five legal values: FORWARD, REQUEST,
>+        INCLUDE, ASYNC, 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 ASYNC means the Filter will be applied under
>+        calls dispatched from an AsyncContext.
>+        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="ASYNC"/>
>+        <xsd:enumeration value="ERROR"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <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.
>+        
>+        Error-page declarations using the exception-type element in
>+        the deployment descriptor must be unique up to the class name of
>+        the exception-type. Similarly, error-page declarations using the
>+        status-code element must be unique in the deployment descriptor
>+        up to the status code.
>+        
>+        Used in: web-app
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:choice minOccurs="0"
>+                  maxOccurs="1">
>+        <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="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"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The fully qualified classname of the filter.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="async-supported"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <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="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="5"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="nonEmptyStringType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This type defines a string which contains at least one
>+        character.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:minLength value="1"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </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="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">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        A HTTP method type as defined in HTTP 1.1 section 2.2.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:token">
>+      <xsd:pattern value="[!-~-[&#60;&#62;@,;:&#34;/\[\]?=\{\}\\\p{Z}]]+"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+  <xsd:simpleType name="load-on-startupType">
>+    <xsd:union memberTypes="javaee:null-charType xsd:integer"/>
>+  </xsd:simpleType>
>+
>+  <xsd:simpleType name="null-charType">
>+    <xsd:restriction base="xsd:string">
>+      <xsd:enumeration value=""/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+
>+
>+
>+  <xsd:complexType name="login-configType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The login-configType is used to configure the authentication
>+        method that should be used, the realm name that should be
>+        used for this application, and the attributes that are
>+        needed by the form login mechanism.
>+        
>+        Used in: web-app
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="auth-method"
>+                   type="javaee:auth-methodType"
>+                   minOccurs="0"/>
>+      <xsd:element name="realm-name"
>+                   type="javaee:string"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The realm name element specifies the realm name to
>+            use in HTTP Basic authorization.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="form-login-config"
>+                   type="javaee:form-login-configType"
>+                   minOccurs="0"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="mime-mappingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The mime-mappingType defines a mapping between an extension
>+        and a mime type.
>+        
>+        Used in: web-app
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:annotation>
>+        <xsd:documentation>
>+
>+          The extension element contains a string describing an
>+          extension. example: "txt"
>+          
>+        </xsd:documentation>
>+      </xsd:annotation>
>+      <xsd:element name="extension"
>+                   type="javaee:string"/>
>+      <xsd:element name="mime-type"
>+                   type="javaee:mime-typeType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="mime-typeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The mime-typeType is used to indicate a defined mime type.
>+        
>+        Example:
>+        "text/plain"
>+        
>+        Used in: mime-mapping
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="security-constraintType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The security-constraintType is used to associate
>+        security constraints with one or more web resource
>+        collections
>+        
>+        Used in: web-app
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="display-name"
>+                   type="javaee:display-nameType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="web-resource-collection"
>+                   type="javaee:web-resource-collectionType"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="auth-constraint"
>+                   type="javaee:auth-constraintType"
>+                   minOccurs="0"/>
>+      <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="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 minOccurs="0"
>+                  maxOccurs="1">
>+        <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="enabled"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <xsd:element name="async-supported"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"/>
>+      <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:element name="multipart-config"
>+                   type="javaee:multipart-configType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </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="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:element name="cookie-config"
>+                   type="javaee:cookie-configType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The cookie-config element defines the configuration of the
>+            session tracking cookies created by this web application.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="tracking-mode"
>+                   type="javaee:tracking-modeType"
>+                   minOccurs="0"
>+                   maxOccurs="3">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The tracking-mode element defines the tracking modes
>+            for sessions created by this web application
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cookie-configType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The cookie-configType defines the configuration for the
>+        session tracking cookies of this web application.
>+        
>+        Used in: session-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="name"
>+                   type="javaee:cookie-nameType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The name that will be assigned to any session tracking
>+            cookies created by this web application.
>+            The default is JSESSIONID
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="domain"
>+                   type="javaee:cookie-domainType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The domain name that will be assigned to any session tracking
>+            cookies created by this web application.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="path"
>+                   type="javaee:cookie-pathType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The path that will be assigned to any session tracking
>+            cookies created by this web application.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="comment"
>+                   type="javaee:cookie-commentType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The comment that will be assigned to any session tracking
>+            cookies created by this web application.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="http-only"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Specifies whether any session tracking cookies created 
>+            by this web application will be marked as HttpOnly
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="secure"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Specifies whether any session tracking cookies created 
>+            by this web application will be marked as secure
>+            even if the request that initiated the corresponding session
>+            is using plain HTTP instead of HTTPS
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-age"
>+                   type="javaee:xsdIntegerType"
>+                   minOccurs="0">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The lifetime (in seconds) that will be assigned to any
>+            session tracking cookies created by this web application.
>+            Default is -1
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cookie-nameType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The name that will be assigned to any session tracking
>+        cookies created by this web application.
>+        The default is JSESSIONID
>+        
>+        Used in: cookie-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:nonEmptyStringType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cookie-domainType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The domain name that will be assigned to any session tracking
>+        cookies created by this web application.
>+        
>+        Used in: cookie-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:nonEmptyStringType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cookie-pathType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The path that will be assigned to any session tracking
>+        cookies created by this web application.
>+        
>+        Used in: cookie-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:nonEmptyStringType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="cookie-commentType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The comment that will be assigned to any session tracking
>+        cookies created by this web application.
>+        
>+        Used in: cookie-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:extension base="javaee:nonEmptyStringType"/>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="tracking-modeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The tracking modes for sessions created by this web
>+        application
>+        
>+        Used in: session-config
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="COOKIE"/>
>+        <xsd:enumeration value="URL"/>
>+        <xsd:enumeration value="SSL"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </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="3.0"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+
>+
>+
>+  <xsd:complexType name="web-resource-collectionType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The web-resource-collectionType is used to identify the
>+        resources and HTTP methods on those resources to which a
>+        security constraint applies. If no HTTP methods are specified,
>+        then the security constraint applies to all HTTP methods.
>+        If HTTP methods are specified by http-method-omission
>+        elements, the security constraint applies to all methods
>+        except those identified in the collection.
>+        http-method-omission and http-method elements are never
>+        mixed in the same collection. 
>+        
>+        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:choice minOccurs="0"
>+                  maxOccurs="1">
>+        <xsd:element name="http-method"
>+                     type="javaee:http-methodType"
>+                     minOccurs="1"
>+                     maxOccurs="unbounded">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              Each http-method names an HTTP method to which the
>+              constraint applies.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="http-method-omission"
>+                     type="javaee:http-methodType"
>+                     minOccurs="1"
>+                     maxOccurs="unbounded">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              Each http-method-omission names an HTTP method to
>+              which the constraint does not apply.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+      </xsd:choice>
>+    </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:simpleType name="localeType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The localeType defines valid locale defined by ISO-639-1
>+        and ISO-3166.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:string">
>+      <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+  <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="locale-encoding-mapping-listType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The locale-encoding-mapping-list contains one or more
>+        locale-encoding-mapping(s).
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="locale-encoding-mapping"
>+                   type="javaee:locale-encoding-mappingType"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="locale-encoding-mappingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The locale-encoding-mapping contains locale name and
>+        encoding name. The locale name must be either "Language-code",
>+        such as "ja", defined by ISO-639 or "Language-code_Country-code",
>+        such as "ja_JP".  "Country code" is defined by ISO-3166.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="locale"
>+                   type="javaee:localeType"/>
>+      <xsd:element name="encoding"
>+                   type="javaee:encodingType"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ordering-othersType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This element indicates that the ordering sub-element in which
>+        it was placed should take special action regarding the ordering
>+        of this application resource relative to other application
>+        configuration resources.
>+        See section 8.2.2 of the specification for details.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="absoluteOrderingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Please see section 8.2.2 of the specification for details.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:choice minOccurs="0"
>+                maxOccurs="unbounded">
>+      <xsd:element name="name"
>+                   type="javaee:java-identifierType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="others"
>+                   type="javaee:ordering-othersType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </xsd:choice>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="orderingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Please see section 8.2.2 of the specification for details.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="after"
>+                   type="javaee:ordering-orderingType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="before"
>+                   type="javaee:ordering-orderingType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="ordering-orderingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This element contains a sequence of "name" elements, each of
>+        which
>+        refers to an application configuration resource by the "name"
>+        declared on its web.xml fragment.  This element can also contain
>+        a single "others" element which specifies that this document
>+        comes
>+        before or after other documents within the application.
>+        See section 8.2.2 of the specification for details.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="name"
>+                   type="javaee:java-identifierType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+      <xsd:element name="others"
>+                   type="javaee:ordering-othersType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="multipart-configType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This element specifies configuration information related to the
>+        handling of multipart/form-data requests.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="location"
>+                   type="javaee:string"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The directory location where uploaded files will be stored
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-file-size"
>+                   type="xsd:long"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The maximum size limit of uploaded files
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="max-request-size"
>+                   type="xsd:long"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The maximum size limit of multipart/form-data requests
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="file-size-threshold"
>+                   type="xsd:integer"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The size threshold after which an uploaded file will be
>+            written to disk
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+</xsd:schema>
>Index: dtdsAndSchemas/javaee_web_services_client_1_3.xsd
>===================================================================
>RCS file: dtdsAndSchemas/javaee_web_services_client_1_3.xsd
>diff -N dtdsAndSchemas/javaee_web_services_client_1_3.xsd
>--- /dev/null	1 Jan 1970 00:00:00 -0000
>+++ dtdsAndSchemas/javaee_web_services_client_1_3.xsd	1 Jan 1970 00:00:00 -0000
>@@ -0,0 +1,737 @@
>+<?xml version="1.0" encoding="UTF-8"?>
>+<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="1.3">
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
>+      
>+      Copyright 2003-2009 Sun Microsystems, Inc. All rights reserved.
>+      
>+      The contents of this file are subject to the terms of either the
>+      GNU General Public License Version 2 only ("GPL") or the Common
>+      Development and Distribution License("CDDL") (collectively, the
>+      "License").  You may not use this file except in compliance with
>+      the License. You can obtain a copy of the License at
>+      https://glassfish.dev.java.net/public/CDDL+GPL.html or
>+      glassfish/bootstrap/legal/LICENSE.txt.  See the License for the
>+      specific language governing permissions and limitations under the
>+      License.
>+      
>+      When distributing the software, include this License Header
>+      Notice in each file and include the License file at
>+      glassfish/bootstrap/legal/LICENSE.txt.  Sun designates this
>+      particular file as subject to the "Classpath" exception as
>+      provided by Sun in the GPL Version 2 section of the License file
>+      that accompanied this code.  If applicable, add the following
>+      below the License Header, with the fields enclosed by brackets []
>+      replaced by your own identifying information:
>+      "Portions Copyrighted [year] [name of copyright owner]"
>+      
>+      Contributor(s):
>+      
>+      If you wish your version of this file to be governed by only the
>+      CDDL or only the GPL Version 2, indicate your decision by adding
>+      "[Contributor] elects to include this software in this
>+      distribution under the [CDDL or GPL Version 2] license."  If you
>+      don't indicate a single choice of license, a recipient has the
>+      option to distribute your version of this file under either the
>+      CDDL, the GPL Version 2 or to extend the choice of license to its
>+      licensees as provided above.  However, if you add GPL Version 2
>+      code and therefore, elected the GPL Version 2 license, then the
>+      option applies only if the new code is made subject to such
>+      option by the copyright holder.
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+  <xsd:annotation>
>+    <xsd:documentation>
>+
>+      (C) Copyright International Business Machines Corporation 2002
>+      
>+    </xsd:documentation>
>+  </xsd:annotation>
>+
>+
>+
>+
>+  <xsd:complexType name="service-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The service-ref element declares a reference to a Web
>+        service. It contains optional description, display name and
>+        icons, a declaration of the required Service interface,
>+        an optional WSDL document location, an optional set
>+        of JAX-RPC mappings, an optional QName for the service element,
>+        an optional set of Service Endpoint Interfaces to be resolved 
>+        by the container to a WSDL port, and an optional set of handlers.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="service-ref-name"
>+                   type="javaee:jndi-nameType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-ref-name element declares logical name that the
>+            components in the module use to look up the Web service. It 
>+            is recommended that all service reference names start with 
>+            "service/".
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-interface"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-interface element declares the fully qualified class
>+            name of the JAX-RPC Service interface the client depends on. 
>+            In most cases the value will be javax.xml.rpc.Service.  A JAX-RPC
>+            generated Service Interface class may also be specified.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-ref-type"
>+                   type="javaee:fully-qualified-classType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-ref-type element declares the type of the service-ref 
>+            element that is injected or returned when a JNDI lookup is done.
>+            This must be either a fully qualified name of Service class or 
>+            the fully qualified name of service endpoint interface class. 
>+            This is only used with JAX-WS runtime where the corresponding 
>+            @WebServiceRef annotation can be used to denote both a Service
>+            or a Port.
>+            
>+            If this is not specified, then the type of service-ref element 
>+            that is injected or returned when a JNDI lookup is done is 
>+            always a Service interface/class.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="wsdl-file"
>+                   type="javaee:xsdAnyURIType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The wsdl-file element contains the URI location of a WSDL
>+            file. The location is relative to the root of the module.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="jaxrpc-mapping-file"
>+                   type="javaee:pathType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The jaxrpc-mapping-file element contains the name of a file that
>+            describes the JAX-RPC mapping between the Java interaces used by
>+            the application and the WSDL description in the wsdl-file.  The 
>+            file name is a relative path within the module file.
>+            
>+            This is not required when JAX-WS based runtime is used.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="service-qname"
>+                   type="javaee:xsdQNameType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-qname element declares the specific WSDL service
>+            element that is being refered to.  It is not specified if no
>+            wsdl-file is declared.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="port-component-ref"
>+                   type="javaee:port-component-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The port-component-ref element declares a client dependency
>+            on the container for resolving a Service Endpoint Interface
>+            to a WSDL port. It optionally associates the Service Endpoint
>+            Interface with a particular port-component. This is only used
>+            by the container for a Service.getPort(Class) method call.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:choice>
>+        <xsd:element name="handler"
>+                     type="javaee:handlerType"
>+                     minOccurs="0"
>+                     maxOccurs="unbounded">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              	Declares the handler for a port-component. Handlers can
>+              	access the init-param name/value pairs using the
>+              	HandlerInfo interface. If port-name is not specified, the
>+              	handler is assumed to be associated with all ports of the
>+              	service.
>+              
>+              	To be used with JAX-RPC based runtime only.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+        <xsd:element name="handler-chains"
>+                     type="javaee:handler-chainsType"
>+                     minOccurs="0"
>+                     maxOccurs="1">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              	 To be used with JAX-WS based runtime only.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+        </xsd:element>
>+      </xsd:choice>
>+      <xsd:group ref="javaee:resourceGroup"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="port-component-refType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The port-component-ref element declares a client dependency
>+        on the container for resolving a Service Endpoint Interface
>+        to a WSDL port. It optionally associates the Service Endpoint
>+        Interface with a particular port-component. This is only used
>+        by the container for a Service.getPort(Class) method call.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="service-endpoint-interface"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The service-endpoint-interface element defines a fully qualified
>+            Java class that represents the Service Endpoint Interface of a
>+            WSDL port.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="enable-mtom"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Used to enable or disable SOAP MTOM/XOP mechanism on the client
>+            side for a port-component. 
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="mtom-threshold"
>+                   type="javaee:xsdNonNegativeIntegerType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            When MTOM is enabled, binary data above this size in bytes
>+            should be XOP encoded or sent as attachment. Default value is 0.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="addressing"
>+                   type="javaee:addressingType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            This specifies the WS-Addressing requirements for a JAX-WS
>+            web service. It corresponds to javax.xml.ws.soap.Addressing
>+            annotation or its feature javax.xml.ws.soap.AddressingFeature.
>+            
>+            See the addressingType for more information.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="respect-binding"
>+                   type="javaee:respect-bindingType"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Corresponds to the javax.xml.ws.RespectBinding annotation
>+            or its corresponding javax.xml.ws.RespectBindingFeature web
>+            service feature. This is used to control whether a JAX-WS
>+            implementation must respect/honor the contents of the
>+            wsdl:binding in the WSDL that is associated with the service.
>+            
>+            Not to be specified for JAX-RPC runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="port-component-link"
>+                   type="javaee:string"
>+                   minOccurs="0"
>+                   maxOccurs="1">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The port-component-link element links a port-component-ref
>+            to a specific port-component required to be made available
>+            by a service reference.
>+            
>+            The value of a port-component-link must be the
>+            port-component-name of a port-component in the same module
>+            or another module in the same application unit. The syntax
>+            for specification follows the syntax defined for ejb-link
>+            in the EJB 2.0 specification.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="handler-chainsType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The handler-chains element defines the handlerchains associated with this
>+        service or service endpoint.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="handler-chain"
>+                   type="javaee:handler-chainType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="handler-chainType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        The handler-chain element defines the handlerchain. 
>+        Handlerchain can be defined such that the handlers in the
>+        handlerchain operate,all ports of a service, on a specific
>+        port or on a list of protocol-bindings. The choice of elements
>+        service-name-pattern, port-name-pattern and protocol-bindings
>+        are used to specify whether the handlers in handler-chain are
>+        for a service, port or protocol binding. If none of these 
>+        choices are specified with the handler-chain element then the
>+        handlers specified in the handler-chain will be applied on 
>+        everything.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:choice minOccurs="0"
>+                  maxOccurs="1">
>+        <xsd:element name="service-name-pattern"
>+                     type="javaee:qname-pattern"/>
>+        <xsd:element name="port-name-pattern"
>+                     type="javaee:qname-pattern"/>
>+        <xsd:element name="protocol-bindings"
>+                     type="javaee:protocol-bindingListType"/>
>+      </xsd:choice>
>+      <xsd:element name="handler"
>+                   type="javaee:handlerType"
>+                   minOccurs="1"
>+                   maxOccurs="unbounded"/>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+  <xsd:simpleType name="protocol-bindingListType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Defines the type used for specifying a list of
>+        protocol-bindingType(s). For e.g.
>+        
>+        ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:list itemType="javaee:protocol-bindingType"/>
>+  </xsd:simpleType>
>+
>+  <xsd:simpleType name="protocol-bindingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Defines the type used for specifying the URI for the
>+        protocol binding used by the port-component.  For
>+        portability one could use one of the following tokens that
>+        alias the standard binding types: 
>+        
>+        ##SOAP11_HTTP
>+        ##SOAP11_HTTP_MTOM
>+        ##SOAP12_HTTP
>+        ##SOAP12_HTTP_MTOM
>+        ##XML_HTTP
>+        
>+        Other specifications could define tokens that start with ##
>+        to alias new standard binding URIs that are introduced.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:union memberTypes="xsd:anyURI javaee:protocol-URIAliasType"/>
>+  </xsd:simpleType>
>+
>+  <xsd:simpleType name="protocol-URIAliasType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Defines the type that is used for specifying tokens that
>+        start with ## which are used to alias existing standard
>+        protocol bindings and support aliases for new standard
>+        binding URIs that are introduced in future specifications.
>+        
>+        The following tokens alias the standard protocol binding
>+        URIs:
>+        
>+        ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
>+        ##SOAP11_HTTP_MTOM = 
>+        "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
>+        ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
>+        ##SOAP12_HTTP_MTOM = 
>+        "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
>+        ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:token">
>+      <xsd:pattern value="##.+"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+  <xsd:simpleType name="qname-pattern">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This is used to specify the QName pattern in the
>+        attribute service-name-pattern and port-name-pattern in
>+        the handler-chain element
>+        
>+        For example, the various forms acceptable here for
>+        service-name-pattern attribute in handler-chain element
>+        are :
>+        
>+        Exact Name: service-name-pattern="ns1:EchoService"
>+        
>+        	 In this case, handlers specified in this
>+        	 handler-chain element will apply to all ports with
>+        	 this exact service name. The namespace prefix must
>+        	 have been declared in a namespace declaration
>+        	 attribute in either the start-tag of the element
>+        	 where the prefix is used or in an an ancestor 
>+        	 element (i.e. an element in whose content the 
>+        	 prefixed markup occurs)
>+        	 
>+        
>+        Pattern : service-name-pattern="ns1:EchoService*"
>+        
>+        	 In this case, handlers specified in this
>+        	 handler-chain element will apply to all ports whose
>+        	 Service names are like EchoService1, EchoServiceFoo
>+        	 etc. The namespace prefix must have been declared in
>+        	 a namespace declaration attribute in either the
>+        	 start-tag of the element where the prefix is used or
>+        	 in an an ancestor element (i.e. an element in whose 
>+        	 content the prefixed markup occurs)
>+        
>+        Wild Card : service-name-pattern="*"
>+        
>+        	In this case, handlers specified in this handler-chain
>+        	element will apply to ports of all service names.
>+        
>+        The same can be applied to port-name attribute in
>+        handler-chain element.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:restriction base="xsd:token">
>+      <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
>+    </xsd:restriction>
>+  </xsd:simpleType>
>+
>+
>+
>+
>+  <xsd:complexType name="addressingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        This specifies the WS-Addressing requirements for a JAX-WS web service.
>+        It corresponds to javax.xml.ws.soap.Addressing annotation or its
>+        feature javax.xml.ws.soap.AddressingFeature.
>+        
>+        If the "enabled" element is "true", WS-Addressing is enabled.
>+        It means that the endpoint supports WS-Addressing but does not require
>+        its use. The default value for "enabled" is "true".
>+        
>+        If the WS-Addressing is enabled and the "required" element is "true",
>+        it means that the endpoint requires WS-Addressing. The default value
>+        for "required" is "false".
>+        
>+        If WS-Addressing is enabled, the "responses" element determines
>+        if an endpoint requires the use of only anonymous responses,
>+        or only non-anonymous responses, or all. The value of the "responses"
>+        element must be one of the following:
>+        
>+        ANONYMOUS
>+        NON_ANONYMOUS
>+        ALL
>+        
>+        The default value for the "responses" is ALL.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="enabled"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="required"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+      <xsd:element name="responses"
>+                   type="javaee:addressing-responsesType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="addressing-responsesType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        If WS-Addressing is enabled, this type determines if an endpoint
>+        requires the use of only anonymous responses, or only non-anonymous
>+        responses, or all.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:simpleContent>
>+      <xsd:restriction base="javaee:string">
>+        <xsd:enumeration value="ANONYMOUS"/>
>+        <xsd:enumeration value="NON_ANONYMOUS"/>
>+        <xsd:enumeration value="ALL"/>
>+      </xsd:restriction>
>+    </xsd:simpleContent>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="respect-bindingType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Corresponds to the javax.xml.ws.RespectBinding annotation
>+        or its corresponding javax.xml.ws.RespectBindingFeature web
>+        service feature. This is used to control whether a JAX-WS
>+        implementation must respect/honor the contents of the
>+        wsdl:binding in the WSDL that is associated with the service.
>+        
>+        If the "enabled" element is "true", wsdl:binding in the
>+        associated WSDL, if any, must be respected/honored.
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:element name="enabled"
>+                   type="javaee:true-falseType"
>+                   minOccurs="0"
>+                   maxOccurs="1"/>
>+    </xsd:sequence>
>+  </xsd:complexType>
>+
>+
>+
>+
>+  <xsd:complexType name="handlerType">
>+    <xsd:annotation>
>+      <xsd:documentation>
>+
>+        Declares the handler for a port-component, service-ref. Handlers can
>+        access the init-param name/value pairs using the HandlerInfo interface.
>+        
>+        Used in: port-component, service-ref
>+        
>+      </xsd:documentation>
>+    </xsd:annotation>
>+    <xsd:sequence>
>+      <xsd:group ref="javaee:descriptionGroup"/>
>+      <xsd:element name="handler-name"
>+                   type="javaee:string">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Defines the name of the handler. The name must be unique within the
>+            module.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="handler-class"
>+                   type="javaee:fully-qualified-classType">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Defines a fully qualified class name for the handler implementation.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="init-param"
>+                   type="javaee:param-valueType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Not to be specified for JAX-WS runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="soap-header"
>+                   type="javaee:xsdQNameType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            Defines the QName of a SOAP header that will be processed by the
>+            handler.
>+            
>+            Not to be specified for JAX-WS runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="soap-role"
>+                   type="javaee:string"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The soap-role element contains a SOAP actor definition that the
>+            Handler will play as a role.
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+      <xsd:element name="port-name"
>+                   type="javaee:string"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:annotation>
>+          <xsd:documentation>
>+
>+            The port-name element defines the WSDL port-name that a
>+            handler should be associated with. If port-name is not
>+            specified, the handler is assumed to be associated with
>+            all ports of the service.
>+            
>+            Not to be specified for JAX-WS runtime
>+            
>+          </xsd:documentation>
>+        </xsd:annotation>
>+      </xsd:element>
>+    </xsd:sequence>
>+    <xsd:attribute name="id"
>+                   type="xsd:ID"/>
>+  </xsd:complexType>
>+
>+  <xsd:group name="service-refGroup">
>+    <xsd:sequence>
>+      <xsd:element name="service-ref"
>+                   type="javaee:service-refType"
>+                   minOccurs="0"
>+                   maxOccurs="unbounded">
>+        <xsd:key name="service-ref_handler-name-key">
>+          <xsd:annotation>
>+            <xsd:documentation>
>+
>+              Defines the name of the handler. The name must be unique
>+              within the module.
>+              
>+            </xsd:documentation>
>+          </xsd:annotation>
>+          <xsd:selector xpath="javaee:handler"/>
>+          <xsd:field xpath="javaee:handler-name"/>
>+        </xsd:key>
>+      </xsd:element>
>+    </xsd:sequence>
>+  </xsd:group>
>+
>+</xsd:schema>

Actions: View | Diff

Attachments on bug 262038: 155391