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

    DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

    Copyright (c) 2010 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:schema
     targetNamespace="http://java.sun.com/xml/ns/javaee"
     xmlns:javaee="http://java.sun.com/xml/ns/javaee"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="qualified"
     attributeFormDefault="unqualified"
     version="5">
  <xsd:annotation>
    <xsd:documentation>
      @(#)javaee_5.xsds	1.65 06/02/17
    </xsd:documentation>
  </xsd:annotation>

  <xsd:annotation>
    <xsd:documentation>

    DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.

    Copyright (c) 2010 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>

The following definitions that appear in the common
shareable schema(s) of J2EE deployment descriptors should be
interpreted with respect to the context they are included:

Deployment Component may indicate one of the following:
    j2ee application;
    application client;
    web application;
    enterprise bean;
    resource adapter;

Deployment File may indicate one of the following:
    ear file;
    war file;
    jar file;
    rar file;

</xsd:documentation>
</xsd:annotation>

  <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
	      schemaLocation="http://www.w3.org/2001/xml.xsd"/>

  <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>


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

  <xsd:group name="descriptionGroup">
    <xsd:annotation>
      <xsd:documentation>

	This group keeps the usage of the contained description related
	elements consistent across Java EE deployment descriptors.

	All elements may occur multiple times with different languages,
	to support localization of the content.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="display-name"
		   type="javaee:display-nameType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="icon"
		   type="javaee:iconType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:group>

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

  <xsd:complexType name="descriptionType">
    <xsd:annotation>
      <xsd:documentation>

	The description type is used by a description element to
	provide text describing the parent element.  The elements
	that use this type should include any information that the
	Deployment Component's Deployment File file producer wants
	to provide to the consumer of the Deployment Component's
	Deployment File (i.e., to the Deployer). Typically, the
	tools used by such a Deployment File consumer will display
	the description when processing the parent element that
	contains the description.

	The lang attribute defines the language that the
	description is provided in. The default value is "en" (English).

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="javaee:xsdStringType">
	<xsd:attribute ref="xml:lang"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:simpleType name="dewey-versionType">
    <xsd:annotation>
      <xsd:documentation>

	This type defines a dewey decimal that is used
	to describe versions of documents.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:restriction base="xsd:token">
      <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
    </xsd:restriction>
  </xsd:simpleType>

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

  <xsd:complexType name="display-nameType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The display-name type contains a short name that is intended
	  to be displayed by tools. It is used by display-name
	  elements.  The display name need not be unique.

	  Example:

	  ...
	     <display-name xml:lang="en">
	       Employee Self Service
	     </display-name>

	  The value of the xml:lang attribute is "en" (English) by default.

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="javaee:string">
	<xsd:attribute ref="xml:lang"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="ejb-linkType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The ejb-linkType is used by ejb-link
	  elements in the ejb-ref or ejb-local-ref elements to specify
	  that an EJB reference is linked to enterprise bean.

	  The value of the ejb-link element must be the ejb-name of an
	  enterprise bean in the same ejb-jar file or in another ejb-jar
	  file in the same Java EE application unit.

	  Alternatively, the name in the ejb-link element may be
	  composed of a path name specifying the ejb-jar containing the
	  referenced enterprise bean with the ejb-name of the target
	  bean appended and separated from the path name by "#".  The
	  path name is relative to the Deployment File containing
	  Deployment Component that is referencing the enterprise
	  bean.  This allows multiple enterprise beans with the same
	  ejb-name to be uniquely identified.

	  Examples:

	      <ejb-link>EmployeeRecord</ejb-link>

	      <ejb-link>../products/product.jar#ProductEJB</ejb-link>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="ejb-local-refType">
    <xsd:annotation>
      <xsd:documentation>

	The ejb-local-refType is used by ejb-local-ref elements for
	the declaration of a reference to an enterprise bean's local
	home or to the local business interface of a 3.0 bean.
        The declaration consists of:

	    - an optional description
	    - the EJB reference name used in the code of the Deployment
	      Component that's referencing the enterprise bean.
	    - the optional expected type of the referenced enterprise bean
	    - the optional expected local interface of the referenced
              enterprise bean or the local business interface of the
              referenced enterprise bean.
	    - the optional expected local home interface of the referenced
              enterprise bean. Not applicable if this ejb-local-ref refers
              to the local business interface of a 3.0 bean.
	    - optional ejb-link information, used to specify the
	      referenced enterprise bean
            - optional elements to define injection of the named enterprise
              bean into a component field or property.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="ejb-ref-name"
		   type="javaee:ejb-ref-nameType"/>
      <xsd:element name="ejb-ref-type"
		   type="javaee:ejb-ref-typeType"
                   minOccurs="0"/>
      <xsd:element name="local-home"
		   type="javaee:local-homeType"
                   minOccurs="0"/>
      <xsd:element name="local"
		   type="javaee:localType"
                   minOccurs="0"/>
      <xsd:element name="ejb-link"
		   type="javaee:ejb-linkType"
		   minOccurs="0"/>
      <xsd:group ref="javaee:resourceGroup"/>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="ejb-ref-nameType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The ejb-ref-name element contains the name of an EJB
	  reference. The EJB reference is an entry in the
	  Deployment Component's environment and is relative to the
	  java:comp/env context.  The name must be unique within the
	  Deployment Component.

	  It is recommended that name is prefixed with "ejb/".

	  Example:

	  <ejb-ref-name>ejb/Payroll</ejb-ref-name>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:jndi-nameType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="ejb-ref-typeType">
    <xsd:annotation>
      <xsd:documentation>

	The ejb-ref-typeType contains the expected type of the
	referenced enterprise bean.

	The ejb-ref-type designates a value
	that must be one of the following:

	    Entity
	    Session

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="Entity"/>
	<xsd:enumeration value="Session"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="ejb-refType">
    <xsd:annotation>
      <xsd:documentation>

	The ejb-refType is used by ejb-ref elements for the
	declaration of a reference to an enterprise bean's home or
        to the remote business interface of a 3.0 bean.
	The declaration consists of:

	    - an optional description
	    - the EJB reference name used in the code of
	      the Deployment Component that's referencing the enterprise
	      bean.
	    - the optional expected type of the referenced enterprise bean
            - the optional remote interface of the referenced enterprise bean
              or the remote business interface of the referenced enterprise
              bean
	    - the optional expected home interface of the referenced
              enterprise bean.  Not applicable if this ejb-ref
              refers to the remote business interface of a 3.0 bean.
	    - optional ejb-link information, used to specify the
	      referenced enterprise bean
            - optional elements to define injection of the named enterprise
              bean into a component field or property

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="ejb-ref-name"
		   type="javaee:ejb-ref-nameType"/>
      <xsd:element name="ejb-ref-type"
		   type="javaee:ejb-ref-typeType"
		   minOccurs="0"/>
      <xsd:element name="home"
		   type="javaee:homeType"
		   minOccurs="0"/>
      <xsd:element name="remote"
		   type="javaee:remoteType"
                   minOccurs="0"/>
      <xsd:element name="ejb-link"
		   type="javaee:ejb-linkType"
		   minOccurs="0"/>
      <xsd:group ref="javaee:resourceGroup"/>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="emptyType">
    <xsd:annotation>
      <xsd:documentation>

	This type is used to designate an empty
	element when used.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="env-entry-type-valuesType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  This type contains the fully-qualified Java type of the
	  environment entry value that is expected by the
	  application's code.

	  The following are the legal values of env-entry-type-valuesType:

	      java.lang.Boolean
	      java.lang.Byte
	      java.lang.Character
	      java.lang.String
	      java.lang.Short
	      java.lang.Integer
	      java.lang.Long
	      java.lang.Float
	      java.lang.Double

	  Example:

	  <env-entry-type>java.lang.Boolean</env-entry-type>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="java.lang.Boolean"/>
	<xsd:enumeration value="java.lang.Byte"/>
	<xsd:enumeration value="java.lang.Character"/>
	<xsd:enumeration value="java.lang.String"/>
	<xsd:enumeration value="java.lang.Short"/>
	<xsd:enumeration value="java.lang.Integer"/>
	<xsd:enumeration value="java.lang.Long"/>
	<xsd:enumeration value="java.lang.Float"/>
	<xsd:enumeration value="java.lang.Double"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="env-entryType">
    <xsd:annotation>
      <xsd:documentation>

	The env-entryType is used to declare an application's
	environment entry. The declaration consists of an optional
	description, the name of the environment entry, a type
	(optional if the value is injected, otherwise required), and
	an optional value.

	It also includes optional elements to define injection of
	the named resource into fields or JavaBeans properties.

	If a value is not specified and injection is requested,
	no injection will occur and no entry of the specified name
	will be created.  This allows an initial value to be
	specified in the source code without being incorrectly
	changed when no override has been specified.

	If a value is not specified and no injection is requested,
	a value must be supplied during deployment.

	This type is used by env-entry elements.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="env-entry-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      The env-entry-name element contains the name of a
	      Deployment Component's environment entry.  The name
	      is a JNDI name relative to the java:comp/env
	      context.  The name must be unique within a
	      Deployment Component. The uniqueness
	      constraints must be defined within the declared
	      context.

	      Example:

	      <env-entry-name>minAmount</env-entry-name>

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="env-entry-type"
		   type="javaee:env-entry-type-valuesType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      The env-entry-type element contains the Java language
	      type of the environment entry.  If an injection target
	      is specified for the environment entry, the type may
	      be omitted, or must match the type of the injection
	      target.  If no injection target is specified, the type
	      is required.

	      Example:

	      <env-entry-type>java.lang.Integer</env-entry-type>

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="env-entry-value"
		   type="javaee:xsdStringType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      The env-entry-value designates the value of a
	      Deployment Component's environment entry. The value
	      must be a String that is valid for the
	      constructor of the specified type that takes a
	      single String parameter, or for java.lang.Character,
	      a single character.

	      Example:

	      <env-entry-value>100.00</env-entry-value>

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="fully-qualified-classType">
    <xsd:annotation>
      <xsd:documentation>

	The elements that use this type designate the name of a
	Java class or interface.  The name is in the form of a
	"binary name", as defined in the JLS.  This is the form
	of name used in Class.forName().  Tools that need the
	canonical name (the name used in source code) will need
	to convert this binary name to the canonical name.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="generic-booleanType">
    <xsd:annotation>
      <xsd:documentation>

	This type defines four different values which can designate
	boolean values. This includes values yes and no which are
	not designated by xsd:boolean

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="true"/>
	<xsd:enumeration value="false"/>
	<xsd:enumeration value="yes"/>
	<xsd:enumeration value="no"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="homeType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The homeType defines the fully-qualified name of
	  an enterprise bean's home interface.

	  Example:

	      <home>com.aardvark.payroll.PayrollHome</home>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:fully-qualified-classType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="iconType">
    <xsd:annotation>
      <xsd:documentation>

	The icon type contains small-icon and large-icon elements
	that specify the file names for small and large GIF, JPEG,
	or PNG icon images used to represent the parent element in a
	GUI tool.

	The xml:lang attribute defines the language that the
	icon file names are provided in. Its value is "en" (English)
	by default.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="small-icon" type="javaee:pathType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      The small-icon element contains the name of a file
	      containing a small (16 x 16) icon image. The file
	      name is a relative path within the Deployment
	      Component's Deployment File.

	      The image may be in the GIF, JPEG, or PNG format.
	      The icon can be used by tools.

	      Example:

	      <small-icon>employee-service-icon16x16.jpg</small-icon>

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
      <xsd:element name="large-icon" type="javaee:pathType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      The large-icon element contains the name of a file
	      containing a large
	      (32 x 32) icon image. The file name is a relative
	      path within the Deployment Component's Deployment
	      File.

	      The image may be in the GIF, JPEG, or PNG format.
	      The icon can be used by tools.

	      Example:

	      <large-icon>employee-service-icon32x32.jpg</large-icon>

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

    </xsd:sequence>

    <xsd:attribute ref="xml:lang"/>
    <xsd:attribute name="id" type="xsd:ID"/>

  </xsd:complexType>

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

  <xsd:complexType name="injection-targetType">
    <xsd:annotation>
      <xsd:documentation>

	An injection target specifies a class and a name within
	that class into which a resource should be injected.

	The injection target class specifies the fully qualified
	class name that is the target of the injection.  The
	Java EE specifications describe which classes can be an
	injection target.

	The injection target name specifies the target within
	the specified class.  The target is first looked for as a
	JavaBeans property name.  If not found, the target is
	looked for as a field name.

	The specified resource will be injected into the target
	during initialization of the class by either calling the
	set method for the target property or by setting a value
	into the named field.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="injection-target-class"
		   type="javaee:fully-qualified-classType"/>
      <xsd:element name="injection-target-name"
		   type="javaee:java-identifierType"/>
    </xsd:sequence>
  </xsd:complexType>

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

  <xsd:complexType name="java-identifierType">
    <xsd:annotation>
      <xsd:documentation>

	The java-identifierType defines a Java identifier.
	The users of this type should further verify that
	the content does not contain Java reserved keywords.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="java-typeType">
    <xsd:annotation>
      <xsd:documentation>

	This is a generic type that designates a Java primitive
	type or a fully qualified name of a Java interface/type,
	or an array of such types.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:pattern value="[^\p{Z}]*"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="jndi-nameType">
    <xsd:annotation>
      <xsd:documentation>

	The jndi-nameType type designates a JNDI name in the
	Deployment Component's environment and is relative to the
	java:comp/env context.  A JNDI name must be unique within the
	Deployment Component.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:group name="jndiEnvironmentRefsGroup">
    <xsd:annotation>
      <xsd:documentation>

	This group keeps the usage of the contained JNDI environment
	reference elements consistent across Java EE deployment descriptors.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="env-entry"
		   type="javaee:env-entryType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="ejb-ref"
		   type="javaee:ejb-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="ejb-local-ref"
		   type="javaee:ejb-local-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:group ref="javaee:service-refGroup"/>
      <xsd:element name="resource-ref"
		   type="javaee:resource-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="resource-env-ref"
		   type="javaee:resource-env-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="message-destination-ref"
		   type="javaee:message-destination-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="persistence-context-ref"
		   type="javaee:persistence-context-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="persistence-unit-ref"
		   type="javaee:persistence-unit-refType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="post-construct"
		   type="javaee:lifecycle-callbackType"
		   minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="pre-destroy"
		   type="javaee:lifecycle-callbackType"
		   minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:group>

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

  <xsd:complexType name="lifecycle-callbackType">
    <xsd:annotation>
      <xsd:documentation>

	The lifecycle-callback type specifies a method on a
	class to be called when a lifecycle event occurs.
	Note that each class may have only one lifecycle callback
        method for any given event and that the method may not
	be overloaded.

        If the lifefycle-callback-class element is missing then
        the class defining the callback is assumed to be the
        component class in scope at the place in the descriptor
        in which the callback definition appears.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="lifecycle-callback-class"
		   type="javaee:fully-qualified-classType"
                   minOccurs="0"/>
      <xsd:element name="lifecycle-callback-method"
		   type="javaee:java-identifierType"/>
    </xsd:sequence>
  </xsd:complexType>

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

  <xsd:complexType name="listenerType">
    <xsd:annotation>
      <xsd:documentation>

	The listenerType indicates the deployment properties for a web
	application listener bean.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:group ref="javaee:descriptionGroup"/>
      <xsd:element name="listener-class"
		   type="javaee:fully-qualified-classType">
	<xsd:annotation>
	  <xsd:documentation>

	    The listener-class element declares a class in the
	    application must be registered as a web
	    application listener bean. The value is the fully
	    qualified classname of the listener class.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="local-homeType">
    <xsd:annotation>
      <xsd:documentation>

	The local-homeType defines the fully-qualified
	name of an enterprise bean's local home interface.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:fully-qualified-classType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="localType">
    <xsd:annotation>
      <xsd:documentation>

	The localType defines the fully-qualified name of an
	enterprise bean's local interface.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:fully-qualified-classType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="message-destination-linkType">
    <xsd:annotation>
      <xsd:documentation>

	The message-destination-linkType is used to link a message
	destination reference or message-driven bean to a message
	destination.

	The Assembler sets the value to reflect the flow of messages
	between producers and consumers in the application.

	The value must be the message-destination-name of a message
	destination in the same Deployment File or in another
	Deployment File in the same Java EE application unit.

	Alternatively, the value may be composed of a path name
	specifying a Deployment File containing the referenced
	message destination with the message-destination-name of the
	destination appended and separated from the path name by
	"#". The path name is relative to the Deployment File
	containing Deployment Component that is referencing the
	message destination.  This allows multiple message
	destinations with the same name to be uniquely identified.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="message-destination-refType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The message-destination-ref element contains a declaration
	  of Deployment Component's reference to a message destination
	  associated with a resource in Deployment Component's
	  environment. It consists of:

		  - an optional description
		  - the message destination reference name
		  - an optional message destination type
		  - an optional specification as to whether
		    the destination is used for
		    consuming or producing messages, or both.
		    if not specified, "both" is assumed.
		  - an optional link to the message destination
		  - optional injection targets

	  The message destination type must be supplied unless an
	  injection target is specified, in which case the type
	  of the target is used.  If both are specified, the type
	  must be assignment compatible with the type of the injection
	  target.

	  Examples:

	  <message-destination-ref>
		  <message-destination-ref-name>jms/StockQueue
		  </message-destination-ref-name>
		  <message-destination-type>javax.jms.Queue
		  </message-destination-type>
		  <message-destination-usage>Consumes
		  </message-destination-usage>
		  <message-destination-link>CorporateStocks
		  </message-destination-link>
	  </message-destination-ref>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="message-destination-ref-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The message-destination-ref-name element specifies
	    the name of a message destination reference; its
	    value is the environment entry name used in
	    Deployment Component code.  The name is a JNDI name
	    relative to the java:comp/env context and must be
	    unique within an ejb-jar (for enterprise beans) or a
	    Deployment File (for others).

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
      <xsd:element name="message-destination-type"
		   type="javaee:message-destination-typeType"
		   minOccurs="0"/>
      <xsd:element name="message-destination-usage"
		   type="javaee:message-destination-usageType"
		   minOccurs="0"/>
      <xsd:element name="message-destination-link"
		   type="javaee:message-destination-linkType"
		   minOccurs="0"/>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>

  </xsd:complexType>

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

  <xsd:complexType name="message-destination-typeType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The message-destination-typeType specifies the type of
	  the destination. The type is specified by the Java interface
	  expected to be implemented by the destination.

	  Example:

	    <message-destination-type>javax.jms.Queue
	    </message-destination-type>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:fully-qualified-classType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="message-destination-usageType">
    <xsd:annotation>
      <xsd:documentation>

	The message-destination-usageType specifies the use of the
	message destination indicated by the reference.  The value
	indicates whether messages are consumed from the message
	destination, produced for the destination, or both.  The
	Assembler makes use of this information in linking producers
	of a destination with its consumers.

	The value of the message-destination-usage element must be
	one of the following:
	    Consumes
	    Produces
	    ConsumesProduces

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="Consumes"/>
	<xsd:enumeration value="Produces"/>
	<xsd:enumeration value="ConsumesProduces"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="message-destinationType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The message-destinationType specifies a message
	  destination. The logical destination described by this
	  element is mapped to a physical destination by the Deployer.

	  The message destination element contains:

		  - an optional description
		  - an optional display-name
		  - an optional icon
		  - a message destination name which must be unique
		    among message destination names within the same
		    Deployment File.
		  - an optional mapped name

	  Example:

	  <message-destination>
		  <message-destination-name>CorporateStocks
		  </message-destination-name>
	  </message-destination>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:group ref="javaee:descriptionGroup"/>
      <xsd:element name="message-destination-name"
		   type="javaee:string">
	<xsd:annotation>
	  <xsd:documentation>

	    The message-destination-name element specifies a
	    name for a message destination.  This name must be
	    unique among the names of message destinations
	    within the Deployment File.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
      <xsd:element name="mapped-name"
		   type="javaee:xsdStringType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      A product specific name that this message destination
	      should be mapped to.  Each message-destination-ref
	      element that references this message destination will
	      define a name in the namespace of the referencing
	      component.  (It's a name in the JNDI java:comp/env
	      namespace.)  Many application servers provide a way to
	      map these local names to names of resources known to the
	      application server.  This mapped name is often a global
	      JNDI name, but may be a name of any form.  Each of the
	      local names should be mapped to this same global name.

	      Application servers are not required to support any
	      particular form or type of mapped name, nor the ability
	      to use mapped names.  The mapped name is
	      product-dependent and often installation-dependent.  No
	      use of a mapped name is portable.

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="param-valueType">
    <xsd:annotation>
      <xsd:documentation>

	This type is a general type that can be used to declare
	parameter/value lists.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="param-name"
		   type="javaee:string">
	<xsd:annotation>
	  <xsd:documentation>

	    The param-name element contains the name of a
	    parameter.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="param-value"
		   type="javaee:xsdStringType">
	<xsd:annotation>
	  <xsd:documentation>

	    The param-value element contains the value of a
	    parameter.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="pathType">
    <xsd:annotation>
      <xsd:documentation>

	The elements that use this type designate either a relative
	path or an absolute path starting with a "/".

	In elements that specify a pathname to a file within the
	same Deployment File, relative filenames (i.e., those not
	starting with "/") are considered relative to the root of
	the Deployment File's namespace.  Absolute filenames (i.e.,
	those starting with "/") also specify names in the root of
	the Deployment File's namespace.  In general, relative names
	are preferred.  The exception is .war files where absolute
	names are preferred for consistency with the Servlet API.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="persistence-context-refType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The persistence-context-ref element contains a declaration
	  of Deployment Component's reference to a persistence context
	  associated within a Deployment Component's
	  environment. It consists of:

		  - an optional description
		  - the persistence context reference name
		  - an optional persistence unit name.  If not specified,
                    the default persistence unit is assumed.
		  - an optional specification as to whether
		    the persistence context type is Transaction or
		    Extended.  If not specified, Transaction is assumed.
                  - an optional list of persistence properties
		  - optional injection targets

	  Examples:

            <persistence-context-ref>
              <persistence-context-ref-name>myPersistenceContext
              </persistence-context-ref-name>
            </persistence-context-ref>

            <persistence-context-ref>
              <persistence-context-ref-name>myPersistenceContext
                </persistence-context-ref-name>
              <persistence-unit-name>PersistenceUnit1
                </persistence-unit-name>
              <persistence-context-type>Extended</persistence-context-type>
            </persistence-context-ref>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="persistence-context-ref-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The persistence-context-ref-name element specifies
	    the name of a persistence context reference; its
	    value is the environment entry name used in
	    Deployment Component code.  The name is a JNDI name
	    relative to the java:comp/env context.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
      <xsd:element name="persistence-unit-name"
		   type="javaee:string"
		   minOccurs="0">
        <xsd:annotation>
	  <xsd:documentation>

            The Application Assembler(or BeanProvider) may use the
            following syntax to avoid the need to rename persistence
            units to have unique names within a Java EE application.

            The Application Assembler specifies the pathname of the
            root of the persistence.xml file for the referenced
            persistence unit and appends the name of the persistence
            unit separated from the pathname by #. The pathname is
            relative to the referencing application component jar file.
            In this manner, multiple persistence units with the same
            persistence unit name may be uniquely identified when the
            Application Assembler cannot change persistence unit names.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="persistence-context-type"
		   type="javaee:persistence-context-typeType"
		   minOccurs="0"/>

      <xsd:element name="persistence-property"
		   type="javaee:propertyType"
		   minOccurs="0"
		   maxOccurs="unbounded">
        <xsd:annotation>
	  <xsd:documentation>

            Used to specify properties for the container or persistence
            provider.  Vendor-specific properties may be included in
            the set of properties.  Properties that are not recognized
            by a vendor must be ignored.  Entries that make use of the
            namespace javax.persistence and its subnamespaces must not
            be used for vendor-specific properties.  The namespace
            javax.persistence is reserved for use by the specification.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>

  </xsd:complexType>

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

  <xsd:complexType name="persistence-context-typeType">
    <xsd:annotation>
      <xsd:documentation>

	The persistence-context-typeType specifies the transactional
	nature of a persistence context reference.

	The value of the persistence-context-type element must be
	one of the following:
	    Transaction
            Extended

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="Transaction"/>
	<xsd:enumeration value="Extended"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="persistence-unit-refType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The persistence-unit-ref element contains a declaration
	  of Deployment Component's reference to a persistence unit
	  associated within a Deployment Component's
	  environment. It consists of:

		  - an optional description
		  - the persistence unit reference name
		  - an optional persistence unit name.  If not specified,
                    the default persistence unit is assumed.
		  - optional injection targets

	  Examples:

            <persistence-unit-ref>
              <persistence-unit-ref-name>myPersistenceUnit
              </persistence-unit-ref-name>
            </persistence-unit-ref>

            <persistence-unit-ref>
              <persistence-unit-ref-name>myPersistenceUnit
                </persistence-unit-ref-name>
              <persistence-unit-name>PersistenceUnit1
                </persistence-unit-name>
            </persistence-unit-ref>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="persistence-unit-ref-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The persistence-unit-ref-name element specifies
	    the name of a persistence unit reference; its
	    value is the environment entry name used in
	    Deployment Component code.  The name is a JNDI name
	    relative to the java:comp/env context.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
      <xsd:element name="persistence-unit-name"
		   type="javaee:string"
		   minOccurs="0">
        <xsd:annotation>
	  <xsd:documentation>

            The Application Assembler(or BeanProvider) may use the
            following syntax to avoid the need to rename persistence
            units to have unique names within a Java EE application.

            The Application Assembler specifies the pathname of the
            root of the persistence.xml file for the referenced
            persistence unit and appends the name of the persistence
            unit separated from the pathname by #. The pathname is
            relative to the referencing application component jar file.
            In this manner, multiple persistence units with the same
            persistence unit name may be uniquely identified when the
            Application Assembler cannot change persistence unit names.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>

  </xsd:complexType>

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

  <xsd:complexType name="propertyType">
    <xsd:annotation>
      <xsd:documentation>

	Specifies a name/value pair.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="name"
		   type="javaee:xsdStringType">
      </xsd:element>
      <xsd:element name="value"
		   type="javaee:xsdStringType">
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="remoteType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The remote element contains the fully-qualified name
	  of the enterprise bean's remote interface.

	  Example:

	      <remote>com.wombat.empl.EmployeeService</remote>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:fully-qualified-classType"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="res-authType">
    <xsd:annotation>
      <xsd:documentation>

	The res-authType specifies whether the Deployment Component
	code signs on programmatically to the resource manager, or
	whether the Container will sign on to the resource manager
	on behalf of the Deployment Component. In the latter case,
	the Container uses information that is supplied by the
	Deployer.

	The value must be one of the two following:

	    Application
	    Container

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="Application"/>
	<xsd:enumeration value="Container"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="res-sharing-scopeType">
    <xsd:annotation>
      <xsd:documentation>

	The res-sharing-scope type specifies whether connections
	obtained through the given resource manager connection
	factory reference can be shared. The value, if specified,
	must be one of the two following:

	    Shareable
	    Unshareable

	The default value is Shareable.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:string">
	<xsd:enumeration value="Shareable"/>
	<xsd:enumeration value="Unshareable"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="resource-env-refType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The resource-env-refType is used to define
	  resource-env-type elements.  It contains a declaration of a
	  Deployment Component's reference to an administered object
	  associated with a resource in the Deployment Component's
	  environment.  It consists of an optional description, the
	  resource environment reference name, and an optional
	  indication of the resource environment reference type
	  expected by the Deployment Component code.

	  It also includes optional elements to define injection of
	  the named resource into fields or JavaBeans properties.

	  The resource environment type must be supplied unless an
	  injection target is specified, in which case the type
	  of the target is used.  If both are specified, the type
	  must be assignment compatible with the type of the injection
	  target.

	  Example:

	  <resource-env-ref>
	      <resource-env-ref-name>jms/StockQueue
	      </resource-env-ref-name>
	      <resource-env-ref-type>javax.jms.Queue
	      </resource-env-ref-type>
	  </resource-env-ref>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="resource-env-ref-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The resource-env-ref-name element specifies the name
	    of a resource environment reference; its value is
	    the environment entry name used in
	    the Deployment Component code.  The name is a JNDI
	    name relative to the java:comp/env context and must
	    be unique within a Deployment Component.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="resource-env-ref-type"
		   type="javaee:fully-qualified-classType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>

	    The resource-env-ref-type element specifies the type
	    of a resource environment reference.  It is the
	    fully qualified name of a Java language class or
	    interface.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="resource-refType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The resource-refType contains a declaration of a
	  Deployment Component's reference to an external resource. It
	  consists of an optional description, the resource manager
	  connection factory reference name, an optional indication of
	  the resource manager connection factory type expected by the
	  Deployment Component code, an optional type of authentication
	  (Application or Container), and an optional specification of
	  the shareability of connections obtained from the resource
	  (Shareable or Unshareable).

	  It also includes optional elements to define injection of
	  the named resource into fields or JavaBeans properties.

	  The connection factory type must be supplied unless an
	  injection target is specified, in which case the type
	  of the target is used.  If both are specified, the type
	  must be assignment compatible with the type of the injection
	  target.

	  Example:

	  <resource-ref>
	      <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
	      <res-type>javax.sql.DataSource</res-type>
	      <res-auth>Container</res-auth>
	      <res-sharing-scope>Shareable</res-sharing-scope>
	  </resource-ref>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="res-ref-name"
		   type="javaee:jndi-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The res-ref-name element specifies the name of a
	    resource manager connection factory reference.
	    The name is a JNDI name relative to the
	    java:comp/env context.
	    The name must be unique within a Deployment File.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="res-type"
		   type="javaee:fully-qualified-classType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>

	    The res-type element specifies the type of the data
	    source. The type is specified by the fully qualified
	    Java language class or interface
	    expected to be implemented by the data source.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="res-auth"
		   type="javaee:res-authType"
		   minOccurs="0"/>

      <xsd:element name="res-sharing-scope"
		   type="javaee:res-sharing-scopeType"
		   minOccurs="0"/>

      <xsd:group ref="javaee:resourceGroup"/>

    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:group name="resourceGroup">
    <xsd:annotation>
      <xsd:documentation>

	This group collects elements that are common to all the
	JNDI resource elements.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
      <xsd:element name="mapped-name"
		   type="javaee:xsdStringType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>
	    <![CDATA[

	      A product specific name that this resource should be
	      mapped to.  The name of this resource, as defined by the
	      resource's name element or defaulted, is a name that is
	      local to the application component using the resource.
	      (It's a name in the JNDI java:comp/env namespace.)  Many
	      application servers provide a way to map these local
	      names to names of resources known to the application
	      server.  This mapped name is often a global JNDI name,
	      but may be a name of any form.

	      Application servers are not required to support any
	      particular form or type of mapped name, nor the ability
	      to use mapped names.  The mapped name is
	      product-dependent and often installation-dependent.  No
	      use of a mapped name is portable.

	      ]]>
	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="injection-target"
		   type="javaee:injection-targetType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:group>

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

  <xsd:complexType name="role-nameType">
    <xsd:annotation>
      <xsd:documentation>

	The role-nameType designates the name of a security role.

	The name must conform to the lexical rules for a token.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:simpleContent>
      <xsd:restriction base="javaee:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="run-asType">
    <xsd:annotation>
      <xsd:documentation>

	The run-asType specifies the run-as identity to be
	used for the execution of a component. It contains an
	optional description, and the name of a security role.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="role-name"
		   type="javaee:role-nameType"/>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="security-role-refType">
    <xsd:annotation>
      <xsd:documentation>

	The security-role-refType contains the declaration of a
	security role reference in a component's or a
	Deployment Component's code. The declaration consists of an
	optional description, the security role name used in the
	code, and an optional link to a security role. If the
	security role is not specified, the Deployer must choose an
	appropriate security role.

      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="role-name"
		   type="javaee:role-nameType">
	<xsd:annotation>
	  <xsd:documentation>

	    The value of the role-name element must be the String used
	    as the parameter to the
	    EJBContext.isCallerInRole(String roleName) method or the
	    HttpServletRequest.isUserInRole(String role) method.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>

      <xsd:element name="role-link"
		   type="javaee:role-nameType"
		   minOccurs="0">
	<xsd:annotation>
	  <xsd:documentation>

	    The role-link element is a reference to a defined
	    security role. The role-link element must contain
	    the name of one of the security roles defined in the
	    security-role elements.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="security-roleType">
    <xsd:annotation>
      <xsd:documentation>
	<![CDATA[

	  The security-roleType contains the definition of a security
	  role. The definition consists of an optional description of
	  the security role, and the security role name.

	  Example:

	      <security-role>
	      <description>
		  This role includes all employees who are authorized
		  to access the employee service application.
	      </description>
	      <role-name>employee</role-name>
	      </security-role>

	  ]]>
      </xsd:documentation>
    </xsd:annotation>

    <xsd:sequence>
      <xsd:element name="description"
		   type="javaee:descriptionType"
		   minOccurs="0"
		   maxOccurs="unbounded"/>
      <xsd:element name="role-name"
		   type="javaee:role-nameType"/>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
  </xsd:complexType>

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

  <xsd:complexType name="string">
    <xsd:annotation>
      <xsd:documentation>

	This is a special string datatype that is defined by Java EE as
	a base type for defining collapsed strings. When schemas
	require trailing/leading space elimination as well as
	collapsing the existing whitespace, this base type may be
	used.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:token">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="true-falseType">
    <xsd:annotation>
      <xsd:documentation>

	This simple type designates a boolean with only two
	permissible values

	- true
	- false

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:restriction base="javaee:xsdBooleanType">
	<xsd:pattern value="(true|false)"/>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="url-patternType">
    <xsd:annotation>
      <xsd:documentation>

	The url-patternType contains the url pattern of the mapping.
	It must follow the rules specified in Section 11.2 of the
	Servlet API Specification. This pattern is assumed to be in
	URL-decoded form and must not contain CR(#xD) or LF(#xA).
	If it contains those characters, the container must inform
	the developer with a descriptive error message.
	The container must preserve all characters including whitespaces.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string"/>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdAnyURIType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:anyURI.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:anyURI">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdBooleanType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:boolean.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:boolean">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdIntegerType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:integer.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:integer">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdNMTOKENType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:NMTOKEN.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:NMTOKEN">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdNonNegativeIntegerType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:nonNegativeInteger.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:nonNegativeInteger">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdPositiveIntegerType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:positiveInteger.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:positiveInteger">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdQNameType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:QName.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:QName">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

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

  <xsd:complexType name="xsdStringType">
    <xsd:annotation>
      <xsd:documentation>

	This type adds an "id" attribute to xsd:string.

      </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
	<xsd:attribute name="id" type="xsd:ID"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>

</xsd:schema>

