<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"

            targetNamespace="http://xmlns.jcp.org/xml/ns/javaee"

            xmlns:javaee="http://xmlns.jcp.org/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://xmlns.jcp.org/xml/ns/javaee

      and indicate the version of the schema by

      using the version element as shown below:

      <application-client xmlns="http://xmlns.jcp.org/xml/ns/javaee"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee 

      	http://xmlns.jcp.org/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://xmlns.jcp.org/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="connection-factory"

                   type="javaee:connection-factory-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="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://xmlns.jcp.org/xml/ns/javaee"

            xmlns:javaee="http://xmlns.jcp.org/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://xmlns.jcp.org/xml/ns/javaee

      and indicate the version of the schema by

      using the version element as shown below:

      <application xmlns="http://xmlns.jcp.org/xml/ns/javaee"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee 

      	http://xmlns.jcp.org/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://xmlns.jcp.org/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="connection-factory"

                   type="javaee:connection-factory-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://xmlns.jcp.org/xml/ns/javaee"

            xmlns:javaee="http://xmlns.jcp.org/xml/ns/javaee"

            xmlns:xsd="http://www.w3.org/2001/XMLSchema"

            elementFormDefault="qualified"

            attributeFormDefault="unqualified"

            version="1.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>

      DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

      Copyright (c) 2003-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 Connector 1.7 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://xmlns.jcp.org/xml/ns/javaee

      and by indicating the version of the schema by

      using the version element as shown below:

      <connector xmlns="http://xmlns.jcp.org/xml/ns/javaee"

      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee

      	 http://xmlns.jcp.org/xml/ns/javaee/connector_1_7.xsd"

      version="1.7">

      ...

      </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://xmlns.jcp.org/xml/ns/javaee/connector_1_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="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.7"

                   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>

<!-- **************************************************** -->