<?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="7">

  <xsd:annotation>

    <xsd:documentation>

      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

      Copyright (c) 2009-2013 Oracle and/or its affiliates. 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_1_1.html

      or packager/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 packager/legal/LICENSE.txt.

      GPL Classpath Exception:

      Oracle designates this particular file as subject to the "Classpath"

      exception as provided by Oracle in the GPL Version 2 section of the License

      file that accompanied this code.

      Modifications:

      If applicable, add the following below the License Header, with the fields

      enclosed by brackets [] replaced by your own identifying information:

      "Portions Copyright [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 7

      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_7.xsd"

      version="7">

      ...

      </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_7.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_7.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:element name="jms-connection-factory"

                   type="javaee:jms-connection-factoryType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="jms-destination"

                   type="javaee:jms-destinationType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="mail-session"

                   type="javaee:mail-sessionType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="connector-resource"

                   type="javaee:connector-resourceType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

    </xsd:sequence>

    <xsd:attribute name="version"

                   type="javaee:dewey-versionType"

                   fixed="7"

                   use="required">

      <xsd:annotation>

        <xsd:documentation>

          The required value for the version is 7.

        </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>

<?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="7">

  <xsd:annotation>

    <xsd:documentation>

      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

      Copyright (c) 2009-2013 Oracle and/or its affiliates. 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_1_1.html

      or packager/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 packager/legal/LICENSE.txt.

      GPL Classpath Exception:

      Oracle designates this particular file as subject to the "Classpath"

      exception as provided by Oracle in the GPL Version 2 section of the License

      file that accompanied this code.

      Modifications:

      If applicable, add the following below the License Header, with the fields

      enclosed by brackets [] replaced by your own identifying information:

      "Portions Copyright [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 7 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_7.xsd"

      version="7">

      ...

      </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_7.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_7.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:element name="jms-connection-factory"

                   type="javaee:jms-connection-factoryType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="jms-destination"

                   type="javaee:jms-destinationType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="mail-session"

                   type="javaee:mail-sessionType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="connector-resource"

                   type="javaee:connector-resourceType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

      <xsd:element name="administered-object"

                   type="javaee:administered-objectType"

                   minOccurs="0"

                   maxOccurs="unbounded"/>

    </xsd:sequence>

    <xsd:attribute name="version"

                   type="javaee:dewey-versionType"

                   fixed="7"

                   use="required">

      <xsd:annotation>

        <xsd:documentation>

          The required value for the version is 7.

        </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>

<?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.2">

  <xsd:annotation>

    <xsd:documentation>

      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

      Copyright (c) 2009-2013 Oracle and/or its affiliates. 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_1_1.html

      or packager/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 packager/legal/LICENSE.txt.

      GPL Classpath Exception:

      Oracle designates this particular file as subject to the "Classpath"

      exception as provided by Oracle in the GPL Version 2 section of the License

      file that accompanied this code.

      Modifications:

      If applicable, add the following below the License Header, with the fields

      enclosed by brackets [] replaced by your own identifying information:

      "Portions Copyright [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.2 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_2.xsd"

      version="3.2">

      ...

      </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_2.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_7.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 file 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, destination or connection factory lookup

        string, subscription name, 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,

            destinationLookup, connectionFactoryLookup, subscriptionName,

            clientId, and shareSubscriptions.

          </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 file 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 file.

        In that case, standard .war file 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 file 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.2"

                   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 file or .war file's deployment descriptor. The name must be

        unique among the names of the enterprise beans in the same

        ejb-jar file 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"

                   minOccurs="2"

                   maxOccurs="2"/>

    </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>