<!ELEMENT %unique; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %unique;
name %NCName; #REQUIRED
- id ID #IMPLIED
- %uniqueAttrs;>
+ id ID #IMPLIED
+ %uniqueAttrs;>
<!ELEMENT %key; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %key;
name %NCName; #REQUIRED
- id ID #IMPLIED
- %keyAttrs;>
+ id ID #IMPLIED
+ %keyAttrs;>
<!ELEMENT %keyref; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %keyref;
name %NCName; #REQUIRED
- refer %QName; #REQUIRED
- id ID #IMPLIED
- %keyrefAttrs;>
+ refer %QName; #REQUIRED
+ id ID #IMPLIED
+ %keyrefAttrs;>
<!ELEMENT %selector; ((%annotation;)?)>
<!ATTLIST %selector;
<!ELEMENT %notation; (%annotation;)?>
<!ATTLIST %notation;
- name %NCName; #REQUIRED
- id ID #IMPLIED
- public CDATA #REQUIRED
- system %URIref; #IMPLIED
- %notationAttrs;>
+ name %NCName; #REQUIRED
+ id ID #IMPLIED
+ public CDATA #REQUIRED
+ system %URIref; #IMPLIED
+ %notationAttrs;>
<!-- Annotation is either application information or documentation -->
<!-- By having these here they are available for datatypes as well
version="1.4">
<xsd:annotation>
<xsd:documentation>
- @(#)j2ee_1_4.xsds 1.43 03/09/16
+ @(#)j2ee_1_4.xsds 1.43 03/09/16
</xsd:documentation>
</xsd:annotation>
</xsd:annotation>
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xsd:include schemaLocation=
- "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
+ "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
- This group keeps the usage of the contained description related
- elements consistent across J2EE deployment descriptors.
+ This group keeps the usage of the contained description related
+ elements consistent across J2EE deployment descriptors.
- All elements may occur multiple times with different languages,
- to support localization of the content.
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:iconType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:group>
<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 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).
+ 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="j2ee:xsdStringType">
- <xsd:attribute ref="xml:lang"/>
+ <xsd:attribute ref="xml:lang"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type defines a dewey decimal which is used
- to describe versions of documents.
+ This type defines a dewey decimal which is used
+ to describe versions of documents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType name="display-nameType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ Example:
- ...
- <display-name xml:lang="en">Employee Self Service</display-name>
+ ...
+ <display-name xml:lang="en">Employee Self Service</display-name>
- The value of the xml:lang attribute is "en" (English) by default.
+ The value of the xml:lang attribute is "en" (English) by default.
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="j2ee:string">
- <xsd:attribute ref="xml:lang"/>
+ <xsd:attribute ref="xml:lang"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ejb-linkType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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 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 J2EE application unit.
+ 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 J2EE 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.
+ 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:
+ Examples:
- <ejb-link>EmployeeRecord</ejb-link>
+ <ejb-link>EmployeeRecord</ejb-link>
- <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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. The declaration consists of:
+ The ejb-local-refType is used by ejb-local-ref elements for
+ the declaration of a reference to an enterprise bean's local
+ home. 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 expected type of the referenced enterprise bean
- - the expected local home and local interfaces of the
- referenced enterprise bean
- - optional ejb-link information, used to specify the
- referenced enterprise bean
+ - an optional description
+ - the EJB reference name used in the code of the Deployment
+ Component that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected local home and local interfaces of the
+ referenced enterprise bean
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="ejb-ref-name"
- type="j2ee:ejb-ref-nameType"/>
+ type="j2ee:ejb-ref-nameType"/>
<xsd:element name="ejb-ref-type"
- type="j2ee:ejb-ref-typeType"/>
+ type="j2ee:ejb-ref-typeType"/>
<xsd:element name="local-home"
- type="j2ee:local-homeType"/>
+ type="j2ee:local-homeType"/>
<xsd:element name="local"
- type="j2ee:localType"/>
+ type="j2ee:localType"/>
<xsd:element name="ejb-link"
- type="j2ee:ejb-linkType"
- minOccurs="0"/>
+ type="j2ee:ejb-linkType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="ejb-ref-nameType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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/".
+ It is recommended that name is prefixed with "ejb/".
- Example:
+ Example:
- <ejb-ref-name>ejb/Payroll</ejb-ref-name>
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:annotation>
<xsd:documentation>
- The ejb-ref-typeType contains the expected type of the
- referenced enterprise bean.
+ 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:
+ The ejb-ref-type designates a value
+ that must be one of the following:
- Entity
- Session
+ Entity
+ Session
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Entity"/>
- <xsd:enumeration value="Session"/>
+ <xsd:enumeration value="Entity"/>
+ <xsd:enumeration value="Session"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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. The
- declaration consists of:
+ The ejb-refType is used by ejb-ref elements for the
+ declaration of a reference to an enterprise bean's home. 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 expected type of the referenced enterprise bean
- - the expected home and remote interfaces of the referenced
- enterprise bean
- - optional ejb-link information, used to specify the
- referenced enterprise bean
+ - an optional description
+ - the EJB reference name used in the code of
+ the Deployment Component that's referencing the enterprise
+ bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="ejb-ref-name"
- type="j2ee:ejb-ref-nameType"/>
+ type="j2ee:ejb-ref-nameType"/>
<xsd:element name="ejb-ref-type"
- type="j2ee:ejb-ref-typeType"/>
+ type="j2ee:ejb-ref-typeType"/>
<xsd:element name="home"
- type="j2ee:homeType"/>
+ type="j2ee:homeType"/>
<xsd:element name="remote"
- type="j2ee:remoteType"/>
+ type="j2ee:remoteType"/>
<xsd:element name="ejb-link"
- type="j2ee:ejb-linkType"
- minOccurs="0"/>
+ type="j2ee:ejb-linkType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type is used to designate an empty
- element when used.
+ This type is used to designate an empty
+ element when used.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType name="env-entry-type-valuesType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- This type contains the fully-qualified Java type of the
- environment entry value that is expected by the
- application's code.
+ 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:
+ The following are the legal values of env-entry-type-valuesType:
- java.lang.Boolean
- java.lang.Byte
- java.lang.Character
- java.lang.String
- java.lang.Short
- java.lang.Integer
- java.lang.Long
- java.lang.Float
- java.lang.Double
+ java.lang.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:
+ Example:
- <env-entry-type>java.lang.Boolean</env-entry-type>
+ <env-entry-type>java.lang.Boolean</env-entry-type>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee: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: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: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, and an
- optional value. If a value is not specified, one must be
- supplied during deployment.
+ 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, and an
+ optional value. If a value is not specified, one must be
+ supplied during deployment.
- It is used by env-entry elements.
+ It is used by env-entry elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="env-entry-name"
- type="j2ee: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>
+ type="j2ee: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="j2ee:env-entry-type-valuesType"/>
+ type="j2ee:env-entry-type-valuesType"/>
<xsd:element name="env-entry-value"
- type="j2ee: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>
+ type="j2ee: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:sequence>
<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.
+ 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: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
+ 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="j2ee:string">
- <xsd:enumeration value="true"/>
- <xsd:enumeration value="false"/>
- <xsd:enumeration value="yes"/>
- <xsd:enumeration value="no"/>
+ <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[
+ <![CDATA[
- The homeType defines the fully-qualified name of
- an enterprise bean's home interface.
+ The homeType defines the fully-qualified name of
+ an enterprise bean's home interface.
- Example:
+ Example:
- <home>com.aardvark.payroll.PayrollHome</home>
+ <home>com.aardvark.payroll.PayrollHome</home>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:annotation>
<xsd:documentation>
- The icon type contains small-icon and large-icon elements
- that specify the file names for small and large GIF or
- JPEG icon images used to represent the parent element in a
- GUI tool.
+ The icon type contains small-icon and large-icon elements
+ that specify the file names for small and large GIF or
+ JPEG 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.
+ 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="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
+ 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 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 either in the JPEG or GIF format.
- The icon can be used by tools.
+ The image may be either in the JPEG or GIF format.
+ The icon can be used by tools.
- Example:
+ Example:
- <small-icon>employee-service-icon16x16.jpg</small-icon>
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="large-icon" type="j2ee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
+ 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 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 either in the JPEG or GIF format.
- The icon can be used by tools.
+ The image may be either in the JPEG or GIF format.
+ The icon can be used by tools.
- Example:
+ Example:
- <large-icon>employee-service-icon32x32.jpg</large-icon>
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<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.
+ 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="j2ee:string">
- <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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="j2ee:string">
- <xsd:pattern value="[^\p{Z}]*"/>
+ <xsd:pattern value="[^\p{Z}]*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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:annotation>
<xsd:documentation>
- This group keeps the usage of the contained JNDI environment
- reference elements consistent across J2EE deployment descriptors.
+ This group keeps the usage of the contained JNDI environment
+ reference elements consistent across J2EE deployment descriptors.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="env-entry"
- type="j2ee:env-entryType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ejb-ref"
- type="j2ee:ejb-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ejb-local-ref"
- type="j2ee:ejb-local-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:ejb-local-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:group ref="j2ee:service-refGroup"/>
<xsd:element name="resource-ref"
- type="j2ee:resource-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="resource-env-ref"
- type="j2ee:resource-env-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="message-destination-ref"
- type="j2ee:message-destination-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:message-destination-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
- The listenerType indicates the deployment properties for a web
- application listener bean.
+ The listenerType indicates the deployment properties for a web
+ application listener bean.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="listener-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee: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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The local-homeType defines the fully-qualified
- name of an enterprise bean's local home interface.
+ The local-homeType defines the fully-qualified
+ name of an enterprise bean's local home interface.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The localType defines the fully-qualified name of an
- enterprise bean's local interface.
+ The localType defines the fully-qualified name of an
+ enterprise bean's local interface.
</xsd:documentation>
</xsd:annotation>
<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 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 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 J2EE application unit.
+ 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 J2EE 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.
+ 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: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
- - the message destination type
- - a specification as to whether the
- destination is used for
- consuming or producing messages, or both
- - a link to the message destination
-
- 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>
-
- ]]>
+ <![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
+ - the message destination type
+ - a specification as to whether the
+ destination is used for
+ consuming or producing messages, or both
+ - a link to the message destination
+
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="message-destination-ref-name"
- type="j2ee: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>
+ type="j2ee: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="j2ee:message-destination-typeType"/>
+ type="j2ee:message-destination-typeType"/>
<xsd:element name="message-destination-usage"
- type="j2ee:message-destination-usageType"/>
+ type="j2ee:message-destination-usageType"/>
<xsd:element name="message-destination-link"
- type="j2ee:message-destination-linkType"
- minOccurs="0"/>
+ type="j2ee:message-destination-linkType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:complexType name="message-destination-typeType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ Example:
- <message-destination-type>javax.jms.Queue
- </message-destination-type>
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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
+ 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="j2ee:string">
- <xsd:enumeration value="Consumes"/>
- <xsd:enumeration value="Produces"/>
- <xsd:enumeration value="ConsumesProduces"/>
+ <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[
+ <![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-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:
+ 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 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.
- Example:
+ Example:
- <message-destination>
- <message-destination-name>CorporateStocks
- </message-destination-name>
- </message-destination>
+ <message-destination>
+ <message-destination-name>CorporateStocks
+ </message-destination-name>
+ </message-destination>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="message-destination-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee: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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- This type is a general type that can be used to declare
- parameter/value lists.
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="param-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- The param-name element contains the name of a
- parameter.
+ The param-name element contains the name of a
+ parameter.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="param-value"
- type="j2ee:xsdStringType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
- The param-value element contains the value of a
- parameter.
+ The param-value element contains the value of a
+ parameter.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The elements that use this type designate either a relative
- path or an absolute path starting with a "/".
+ 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.
+ 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:complexType name="remoteType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- The remote element contains the fully-qualified name
- of the enterprise bean's remote interface.
+ The remote element contains the fully-qualified name
+ of the enterprise bean's remote interface.
- Example:
+ Example:
- <remote>com.wombat.empl.EmployeeService</remote>
+ <remote>com.wombat.empl.EmployeeService</remote>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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:
+ The value must be one of the two following:
- Application
- Container
+ Application
+ Container
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Application"/>
- <xsd:enumeration value="Container"/>
+ <xsd:enumeration value="Application"/>
+ <xsd:enumeration value="Container"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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:
+ 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
+ Shareable
+ Unshareable
- The default value is Shareable.
+ The default value is Shareable.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="Shareable"/>
- <xsd:enumeration value="Unshareable"/>
+ <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 indication of
- the resource environment reference type expected by the
- Deployment Component code.
-
- 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>
-
- ]]>
+ <![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 indication of
+ the resource environment reference type expected by the
+ Deployment Component code.
+
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="resource-env-ref-name"
- type="j2ee: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>
+ type="j2ee: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="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<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, the indication of the
- resource manager connection factory type expected by the
- Deployment Component code, the type of authentication
- (Application or Container), and an optional specification of
- the shareability of connections obtained from the resource
- (Shareable or Unshareable).
-
- 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>
-
- ]]>
+ <![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, the indication of the
+ resource manager connection factory type expected by the
+ Deployment Component code, the type of authentication
+ (Application or Container), and an optional specification of
+ the shareability of connections obtained from the resource
+ (Shareable or Unshareable).
+
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="res-ref-name"
- type="j2ee: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>
+ type="j2ee: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="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="res-auth"
- type="j2ee:res-authType"/>
+ type="j2ee:res-authType"/>
<xsd:element name="res-sharing-scope"
- type="j2ee:res-sharing-scopeType"
- minOccurs="0"/>
+ type="j2ee:res-sharing-scopeType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The role-nameType designates the name of a security role.
+ The role-nameType designates the name of a security role.
- The name must conform to the lexical rules for a token.
+ The name must conform to the lexical rules for a token.
</xsd:documentation>
</xsd:annotation>
<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.
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="j2ee:role-nameType"/>
+ type="j2ee:role-nameType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<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.
+ 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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="j2ee:role-nameType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee: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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="role-link"
- type="j2ee: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>
+ type="j2ee: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 name="security-roleType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ 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>
+ <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="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="j2ee:role-nameType"/>
+ type="j2ee:role-nameType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This is a special string datatype that is defined by J2EE 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.
+ This is a special string datatype that is defined by J2EE 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This simple type designates a boolean with only two
- permissible values
+ This simple type designates a boolean with only two
+ permissible values
- - true
- - false
+ - true
+ - false
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:xsdBooleanType">
- <xsd:pattern value="(true|false)"/>
+ <xsd:pattern value="(true|false)"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:anyURI.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:boolean.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:integer.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:NMTOKEN.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:nonNegativeInteger.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:positiveInteger.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:QName.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:string.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
limitations under the License.
-->
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.1">
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.1">
<xsd:annotation>
<xsd:documentation>
- @(#)j2ee_web_services_1_1.xsds 1.11 02/11/03
+ @(#)j2ee_web_services_1_1.xsds 1.11 02/11/03
</xsd:documentation>
</xsd:annotation>
<xsd:documentation>
<![CDATA[
- The webservices element is the root element for the web services
- deployment descriptor. It specifies the set of web service
- descriptions that are to be deployed into the J2EE Application
- Server and the dependencies they have on container resources and
- services. The deployment descriptor must be named
- "META-INF/webservices.xml" in the web services' jar file.
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the J2EE Application
+ Server and the dependencies they have on container resources and
+ services. The deployment descriptor must be named
+ "META-INF/webservices.xml" in the web services' jar file.
- Used in: webservices.xml
+ Used in: webservices.xml
- All webservices deployment descriptors must indicate the
- webservices schema by using the J2EE namespace:
+ All webservices deployment descriptors must indicate the
+ webservices schema by using the J2EE namespace:
- http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee
- and by indicating the version of the schema by using the version
- element as shown below:
+ and by indicating the version of the schema by using the version
+ element as shown below:
- <webservices xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
- http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
- version="1.1">
- ...
- </webservices>
+ <webservices xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
+ version="1.1">
+ ...
+ </webservices>
- The instance documents may indicate the published version of the
- schema using the xsi:schemaLocation attribute for the J2EE
- namespace with the following location:
+ The instance documents may indicate the published version of the
+ schema using the xsi:schemaLocation attribute for the J2EE
+ namespace with the following location:
- http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd
+ http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
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.
+ 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:annotation>
<xsd:documentation>
- The webservices element is the root element for the web services
- deployment descriptor. It specifies the set of web service
- descriptions that are to be deployed into the J2EE Application Server
- and the dependencies they have on container resources and services.
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the J2EE Application Server
+ and the dependencies they have on container resources and services.
- Used in: webservices.xml
+ Used in: webservices.xml
</xsd:documentation>
</xsd:annotation>
<xsd:key name="webservice-description-name-key">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The webservice-description-name identifies the collection of
- port-components associated with a WSDL file and JAX-RPC mapping. The
- name must be unique within the deployment descriptor.
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC mapping. The
+ name must be unique within the deployment descriptor.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:webservice-description"/>
<xsd:field xpath="j2ee:webservice-description-name"/>
<xsd:annotation>
<xsd:documentation>
- The port-component element associates a WSDL port with a web service
- interface and implementation. It defines the name of the port as a
- component, optional description, optional display name, optional iconic
- representations, WSDL port QName, Service Endpoint Interface, Service
- Implementation Bean.
+ The port-component element associates a WSDL port with a web service
+ interface and implementation. It defines the name of the port as a
+ component, optional description, optional display name, optional iconic
+ representations, WSDL port QName, Service Endpoint Interface, Service
+ Implementation Bean.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:iconType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="port-component-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
-
- The port-component-name element specifies a port component's
- name. This name is assigned by the module producer to name
- the service implementation bean in the module's deployment
- descriptor. The name must be unique among the port component
- names defined in the same module.
-
- Used in: port-component
-
- Example:
- <port-component-name>EmployeeService
- </port-component-name>
-
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port component's
+ name. This name is assigned by the module producer to name
+ the service implementation bean in the module's deployment
+ descriptor. The name must be unique among the port component
+ names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+
<port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-port"
- type="j2ee:xsdQNameType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name space and local name part of the WSDL port QName.
+ Defines the name space and local name part of the WSDL port QName.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-endpoint-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
- The service-endpoint-interface element contains the
- fully-qualified name of the port component's Service Endpoint
- Interface.
+ The service-endpoint-interface element contains the
+ fully-qualified name of the port component's Service Endpoint
+ Interface.
- Used in: port-component
+ Used in: port-component
- Example:
- <remote>com.wombat.empl.EmployeeService</remote>
+ Example:
+ <remote>com.wombat.empl.EmployeeService</remote>
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-impl-bean"
- type="j2ee:service-impl-beanType"/>
+ type="j2ee:service-impl-beanType"/>
<xsd:element name="handler"
- type="j2ee:port-component_handlerType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:port-component_handlerType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- Declares the handler for a port-component. Handlers can access the
- init-param name/value pairs using the HandlerInfo interface.
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface.
- Used in: port-component
+ Used in: port-component
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="handler-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name of the handler. The name must be unique within the
- module.
+ Defines the name of the handler. The name must be unique within the
+ module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="handler-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines a fully qualified class name for the handler implementation.
+ Defines a fully qualified class name for the handler implementation.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="soap-header"
- type="j2ee:xsdQNameType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the QName of a SOAP header that will be processed by the
- handler.
+ Defines the QName of a SOAP header that will be processed by the
+ handler.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="soap-role"
- type="j2ee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The soap-role element contains a SOAP actor definition that the
- Handler will play as a role.
+ The soap-role element contains a SOAP actor definition that the
+ Handler will play as a role.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The service-impl-bean element defines the web service implementation.
- A service implementation can be an EJB bean class or JAX-RPC web
- component. Existing EJB implementations are exposed as a web service
- using an ejb-link.
+ The service-impl-bean element defines the web service implementation.
+ A service implementation can be an EJB bean class or JAX-RPC web
+ component. Existing EJB implementations are exposed as a web service
+ using an ejb-link.
- Used in: port-component
+ Used in: port-component
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="ejb-link"
- type="j2ee:ejb-linkType"/>
+ type="j2ee:ejb-linkType"/>
<xsd:element name="servlet-link"
- type="j2ee:servlet-linkType"/>
+ type="j2ee:servlet-linkType"/>
</xsd:choice>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="servlet-linkType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- The servlet-link element is used in the service-impl-bean element
- to specify that a Service Implementation Bean is defined as a
- JAX-RPC Service Endpoint.
+ The servlet-link element is used in the service-impl-bean element
+ to specify that a Service Implementation Bean is defined as a
+ JAX-RPC Service Endpoint.
- The value of the servlet-link element must be the servlet-name of
- a JAX-RPC Service Endpoint in the same WAR file.
+ The value of the servlet-link element must be the servlet-name of
+ a JAX-RPC Service Endpoint in the same WAR file.
- Used in: service-impl-bean
+ Used in: service-impl-bean
- Example:
- <servlet-link>StockQuoteService</servlet-link>
+ Example:
+ <servlet-link>StockQuoteService</servlet-link>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:annotation>
<xsd:documentation>
- The webservice-description element defines a WSDL document file
- and the set of Port components associated with the WSDL ports
- defined in the WSDL document. There may be multiple
- webservice-descriptions defined within a module.
+ The webservice-description element defines a WSDL document file
+ and the set of Port components associated with the WSDL ports
+ defined in the WSDL document. There may be multiple
+ webservice-descriptions defined within a module.
- All WSDL file ports must have a corresponding port-component element
- defined.
+ All WSDL file ports must have a corresponding port-component element
+ defined.
- Used in: webservices
+ Used in: webservices
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="icon"
- type="j2ee:iconType"
- minOccurs="0" maxOccurs="1"/>
+ type="j2ee:iconType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="webservice-description-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- The webservice-description-name identifies the collection of
- port-components associated with a WSDL file and JAX-RPC
- mapping. The name must be unique within the deployment descriptor.
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC
+ mapping. The name must be unique within the deployment descriptor.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-file"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
- The wsdl-file element contains the name of a WSDL file in the
- module. The file name is a relative path within the module.
+ The wsdl-file element contains the name of a WSDL file in the
+ module. The file name is a relative path within the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="jaxrpc-mapping-file"
- type="j2ee:pathType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
- The jaxrpc-mapping-file element contains the name of a file that
- describes the JAX-RPC mapping between the Java interaces used by
- the application and the WSDL description in the wsdl-file. The
- file name is a relative path within the module.
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-component"
- type="j2ee:port-componentType"
- minOccurs="1" maxOccurs="unbounded">
- <xsd:key name="port-component_handler-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- Defines the name of the handler. The name must be unique
- within the module.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:handler"/>
- <xsd:field xpath="j2ee:handler-name"/>
- </xsd:key>
+ type="j2ee:port-componentType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:handler"/>
+ <xsd:field xpath="j2ee:handler-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="webservice-description"
- type="j2ee:webservice-descriptionType"
- minOccurs="1" maxOccurs="unbounded">
- <xsd:key name="port-component-name-key">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
-
- The port-component-name element specifies a port
- component's name. This name is assigned by the module
- producer to name the service implementation bean in the
- module's deployment descriptor. The name must be unique
- among the port component names defined in the same module.
-
- Used in: port-component
-
- Example:
- <port-component-name>EmployeeService
- </port-component-name>
-
- ]]>
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:port-component"/>
- <xsd:field xpath="j2ee:port-component-name"/>
- </xsd:key>
+ type="j2ee:webservice-descriptionType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port
+ component's name. This name is assigned by the module
+ producer to name the service implementation bean in the
+ module's deployment descriptor. The name must be unique
+ among the port component names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+
<port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:port-component"/>
+ <xsd:field xpath="j2ee:port-component-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="version"
- type="j2ee:dewey-versionType"
- fixed="1.1"
- use="required">
+ type="j2ee:dewey-versionType"
+ fixed="1.1"
+ use="required">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The required value for the version is 1.1.
+ The required value for the version is 1.1.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="id" type="xsd:ID"/>
limitations under the License.
-->
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.1">
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.1">
<xsd:annotation>
<xsd:documentation>
- @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
+ @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The port-component-ref element declares a client dependency
- on the container for resolving a Service Endpoint Interface
- to a WSDL port. It optionally associates the Service Endpoint
- Interface with a particular port-component. This is only used
- by the container for a Service.getPort(Class) method call.
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="service-endpoint-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-endpoint-interface element defines a fully qualified
- Java class that represents the Service Endpoint Interface of a
- WSDL port.
+ The service-endpoint-interface element defines a fully qualified
+ Java class that represents the Service Endpoint Interface of a
+ WSDL port.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-component-link"
- type="j2ee:string"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
-
- The port-component-link element links a port-component-ref
- to a specific port-component required to be made available
- by a service reference.
-
- The value of a port-component-link must be the
- port-component-name of a port-component in the same module
- or another module in the same application unit. The syntax
- for specification follows the syntax defined for ejb-link
- in the EJB 2.0 specification.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-link element links a port-component-ref
+ to a specific port-component required to be made available
+ by a service reference.
+
+ The value of a port-component-link must be the
+ port-component-name of a port-component in the same module
+ or another module in the same application unit. The syntax
+ for specification follows the syntax defined for ejb-link
+ in the EJB 2.0 specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:group name="service-refGroup">
<xsd:sequence>
<xsd:element name="service-ref"
- type="j2ee:service-refType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:key name="service-ref_handler-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- Defines the name of the handler. The name must be unique
- within the module.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="j2ee:handler"/>
- <xsd:field xpath="j2ee:handler-name"/>
- </xsd:key>
+ type="j2ee:service-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:key name="service-ref_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:handler"/>
+ <xsd:field xpath="j2ee:handler-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
- The service-ref element declares a reference to a Web
- service. It contains optional description, display name and
- icons, a declaration of the required Service interface,
- an optional WSDL document location, an optional set
- of JAX-RPC mappings, an optional QName for the service element,
- an optional set of Service Endpoint Interfaces to be resolved
- by the container to a WSDL port, and an optional set of handlers.
+ The service-ref element declares a reference to a Web
+ service. It contains optional description, display name and
+ icons, a declaration of the required Service interface,
+ an optional WSDL document location, an optional set
+ of JAX-RPC mappings, an optional QName for the service element,
+ an optional set of Service Endpoint Interfaces to be resolved
+ by the container to a WSDL port, and an optional set of handlers.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="service-ref-name"
- type="j2ee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-ref-name element declares logical name that the
- components in the module use to look up the Web service. It
- is recommended that all service reference names start with
- "service/".
+ The service-ref-name element declares logical name that the
+ components in the module use to look up the Web service. It
+ is recommended that all service reference names start with
+ "service/".
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-interface"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-interface element declares the fully qualified class
- name of the JAX-RPC Service interface the client depends on.
- In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
- generated Service Interface class may also be specified.
+ The service-interface element declares the fully qualified class
+ name of the JAX-RPC Service interface the client depends on.
+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
+ generated Service Interface class may also be specified.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-file"
- type="j2ee:xsdAnyURIType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdAnyURIType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The wsdl-file element contains the URI location of a WSDL
- file. The location is relative to the root of the module.
+ The wsdl-file element contains the URI location of a WSDL
+ file. The location is relative to the root of the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="jaxrpc-mapping-file"
- type="j2ee:pathType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
-
- The jaxrpc-mapping-file element contains the name of a file that
- describes the JAX-RPC mapping between the Java interaces used by
- the application and the WSDL description in the wsdl-file. The
- file name is a relative path within the module file.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module file.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-qname"
- type="j2ee:xsdQNameType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-qname element declares the specific WSDL service
- element that is being refered to. It is not specified if no
- wsdl-file is declared.
+ The service-qname element declares the specific WSDL service
+ element that is being refered to. It is not specified if no
+ wsdl-file is declared.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-component-ref"
- type="j2ee:port-component-refType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The port-component-ref element declares a client dependency
- on the container for resolving a Service Endpoint Interface
- to a WSDL port. It optionally associates the Service Endpoint
- Interface with a particular port-component. This is only used
- by the container for a Service.getPort(Class) method call.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:port-component-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="handler"
- type="j2ee:service-ref_handlerType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- Declares the handler for a port-component. Handlers can
- access the init-param name/value pairs using the
- HandlerInfo interface. If port-name is not specified, the
- handler is assumed to be associated with all ports of the
- service.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:service-ref_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can
+ access the init-param name/value pairs using the
+ HandlerInfo interface. If port-name is not specified, the
+ handler is assumed to be associated with all ports of the
+ service.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- Declares the handler for a port-component. Handlers can access the
- init-param name/value pairs using the HandlerInfo interface. If
- port-name is not specified, the handler is assumed to be associated
- with all ports of the service.
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface. If
+ port-name is not specified, the handler is assumed to be associated
+ with all ports of the service.
- Used in: service-ref
+ Used in: service-ref
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="handler-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name of the handler. The name must be unique
- within the module.
+ Defines the name of the handler. The name must be unique
+ within the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="handler-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines a fully qualified class name for the handler
- implementation.
+ Defines a fully qualified class name for the handler
+ implementation.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="soap-header"
- type="j2ee:xsdQNameType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the QName of a SOAP header that will be processed
- by the handler.
+ Defines the QName of a SOAP header that will be processed
+ by the handler.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="soap-role"
- type="j2ee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The soap-role element contains a SOAP actor definition that
- the Handler will play as a role.
+ The soap-role element contains a SOAP actor definition that
+ the Handler will play as a role.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-name"
- type="j2ee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The port-name element defines the WSDL port-name that a
- handler should be associated with.
+ The port-name element defines the WSDL port-name that a
+ handler should be associated with.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
version="5">
<xsd:annotation>
<xsd:documentation>
- @(#)javaee_5.xsds 1.65 06/02/17
+ @(#)javaee_5.xsds 1.65 06/02/17
</xsd:documentation>
</xsd:annotation>
</xsd:annotation>
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"
- schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
<xsd:annotation>
<xsd:documentation>
- This group keeps the usage of the contained description related
- elements consistent across Java EE deployment descriptors.
+ 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.
+ 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"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="display-name"
- type="javaee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="javaee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="icon"
- type="javaee:iconType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="javaee:iconType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:group>
<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 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).
+ 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:attribute ref="xml:lang"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type defines a dewey decimal that is used
- to describe versions of documents.
+ This type defines a dewey decimal that is used
+ to describe versions of documents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType name="display-nameType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ Example:
- ...
- <display-name xml:lang="en">
- Employee Self Service
- </display-name>
+ ...
+ <display-name xml:lang="en">
+ Employee Self Service
+ </display-name>
- The value of the xml:lang attribute is "en" (English) by default.
+ 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:attribute ref="xml:lang"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="ejb-linkType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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 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.
+ 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.
+ 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:
+ Examples:
- <ejb-link>EmployeeRecord</ejb-link>
+ <ejb-link>EmployeeRecord</ejb-link>
- <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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
+ - 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
+ - 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 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:sequence>
<xsd:element name="description"
- type="javaee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="ejb-ref-name"
- type="javaee:ejb-ref-nameType"/>
+ type="javaee:ejb-ref-nameType"/>
<xsd:element name="ejb-ref-type"
- type="javaee:ejb-ref-typeType"
+ type="javaee:ejb-ref-typeType"
minOccurs="0"/>
<xsd:element name="local-home"
- type="javaee:local-homeType"
+ type="javaee:local-homeType"
minOccurs="0"/>
<xsd:element name="local"
- type="javaee:localType"
+ type="javaee:localType"
minOccurs="0"/>
<xsd:element name="ejb-link"
- type="javaee:ejb-linkType"
- minOccurs="0"/>
+ type="javaee:ejb-linkType"
+ minOccurs="0"/>
<xsd:group ref="javaee:resourceGroup"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:complexType name="ejb-ref-nameType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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/".
+ It is recommended that name is prefixed with "ejb/".
- Example:
+ Example:
- <ejb-ref-name>ejb/Payroll</ejb-ref-name>
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:annotation>
<xsd:documentation>
- The ejb-ref-typeType contains the expected type of the
- referenced enterprise bean.
+ 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:
+ The ejb-ref-type designates a value
+ that must be one of the following:
- Entity
- Session
+ Entity
+ Session
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="javaee:string">
- <xsd:enumeration value="Entity"/>
- <xsd:enumeration value="Session"/>
+ <xsd:enumeration value="Entity"/>
+ <xsd:enumeration value="Session"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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
+ 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:
+ 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
+ - 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
+ - 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 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:sequence>
<xsd:element name="description"
- type="javaee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="ejb-ref-name"
- type="javaee:ejb-ref-nameType"/>
+ type="javaee:ejb-ref-nameType"/>
<xsd:element name="ejb-ref-type"
- type="javaee:ejb-ref-typeType"
- minOccurs="0"/>
+ type="javaee:ejb-ref-typeType"
+ minOccurs="0"/>
<xsd:element name="home"
- type="javaee:homeType"
- minOccurs="0"/>
+ type="javaee:homeType"
+ minOccurs="0"/>
<xsd:element name="remote"
- type="javaee:remoteType"
+ type="javaee:remoteType"
minOccurs="0"/>
<xsd:element name="ejb-link"
- type="javaee:ejb-linkType"
- minOccurs="0"/>
+ type="javaee:ejb-linkType"
+ minOccurs="0"/>
<xsd:group ref="javaee:resourceGroup"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- This type is used to designate an empty
- element when used.
+ This type is used to designate an empty
+ element when used.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType name="env-entry-type-valuesType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- This type contains the fully-qualified Java type of the
- environment entry value that is expected by the
- application's code.
+ 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:
+ The following are the legal values of env-entry-type-valuesType:
- java.lang.Boolean
- java.lang.Byte
- java.lang.Character
- java.lang.String
- java.lang.Short
- java.lang.Integer
- java.lang.Long
- java.lang.Float
- java.lang.Double
+ java.lang.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:
+ Example:
- <env-entry-type>java.lang.Boolean</env-entry-type>
+ <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: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: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.
+ 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.
+ 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 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.
+ 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.
+ 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"/>
+ 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>
+ 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>
+ 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>
+ 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: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.
+ 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: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
+ 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: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[
+ <![CDATA[
- The homeType defines the fully-qualified name of
- an enterprise bean's home interface.
+ The homeType defines the fully-qualified name of
+ an enterprise bean's home interface.
- Example:
+ Example:
- <home>com.aardvark.payroll.PayrollHome</home>
+ <home>com.aardvark.payroll.PayrollHome</home>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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.
+ 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[
+ 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 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.
+ The image may be in the GIF, JPEG, or PNG format.
+ The icon can be used by tools.
- Example:
+ Example:
- <small-icon>employee-service-icon16x16.jpg</small-icon>
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="large-icon" type="javaee:pathType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
+ 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 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.
+ The image may be in the GIF, JPEG, or PNG format.
+ The icon can be used by tools.
- Example:
+ Example:
- <large-icon>employee-service-icon32x32.jpg</large-icon>
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:annotation>
<xsd:documentation>
- An injection target specifies a class and a name within
- that class into which a resource should be injected.
+ 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 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 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.
+ 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"/>
+ type="javaee:fully-qualified-classType"/>
<xsd:element name="injection-target-name"
- type="javaee:java-identifierType"/>
+ type="javaee:java-identifierType"/>
</xsd:sequence>
</xsd:complexType>
<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.
+ 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:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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:pattern value="[^\p{Z}]*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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:annotation>
<xsd:documentation>
- This group keeps the usage of the contained JNDI environment
- reference elements consistent across Java EE deployment descriptors.
+ 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"/>
+ type="javaee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ejb-ref"
- type="javaee:ejb-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="ejb-local-ref"
- type="javaee:ejb-local-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ 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"/>
+ type="javaee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="resource-env-ref"
- type="javaee:resource-env-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="message-destination-ref"
- type="javaee:message-destination-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:message-destination-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="persistence-context-ref"
- type="javaee:persistence-context-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:persistence-context-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="persistence-unit-ref"
- type="javaee:persistence-unit-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:persistence-unit-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="post-construct"
- type="javaee:lifecycle-callbackType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="pre-destroy"
- type="javaee:lifecycle-callbackType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:group>
<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
+ 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.
+ be overloaded.
If the lifefycle-callback-class element is missing then
the class defining the callback is assumed to be the
</xsd:annotation>
<xsd:sequence>
<xsd:element name="lifecycle-callback-class"
- type="javaee:fully-qualified-classType"
+ type="javaee:fully-qualified-classType"
minOccurs="0"/>
<xsd:element name="lifecycle-callback-method"
- type="javaee:java-identifierType"/>
+ type="javaee:java-identifierType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The listenerType indicates the deployment properties for a web
- application listener bean.
+ 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>
+ 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.
+ 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:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The local-homeType defines the fully-qualified
- name of an enterprise bean's local home interface.
+ The local-homeType defines the fully-qualified
+ name of an enterprise bean's local home interface.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The localType defines the fully-qualified name of an
- enterprise bean's local interface.
+ The localType defines the fully-qualified name of an
+ enterprise bean's local interface.
</xsd:documentation>
</xsd:annotation>
<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 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 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.
+ 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.
+ 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: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>
-
- ]]>
+ <![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"/>
+ 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>
+ 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"/>
+ type="javaee:message-destination-typeType"
+ minOccurs="0"/>
<xsd:element name="message-destination-usage"
- type="javaee:message-destination-usageType"
- minOccurs="0"/>
+ type="javaee:message-destination-usageType"
+ minOccurs="0"/>
<xsd:element name="message-destination-link"
- type="javaee:message-destination-linkType"
- minOccurs="0"/>
+ type="javaee:message-destination-linkType"
+ minOccurs="0"/>
<xsd:group ref="javaee:resourceGroup"/>
<xsd:complexType name="message-destination-typeType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ Example:
- <message-destination-type>javax.jms.Queue
- </message-destination-type>
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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
+ 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: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[
+ <![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-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:
+ The message destination element contains:
- - an optional description
- - an optional display-name
- - an optional icon
- - a message destination name which must be unique
- among message destination names within the same
- Deployment File.
- - an optional mapped name
+ - an optional 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:
+ Example:
- <message-destination>
- <message-destination-name>CorporateStocks
- </message-destination-name>
- </message-destination>
+ <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>
+ 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.
+ 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: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>
+ 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:annotation>
<xsd:documentation>
- This type is a general type that can be used to declare
- parameter/value lists.
+ 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"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="param-name"
- type="javaee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- The param-name element contains the name of a
- parameter.
+ The param-name element contains the name of a
+ parameter.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="param-value"
- type="javaee:xsdStringType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
- The param-value element contains the value of a
- parameter.
+ The param-value element contains the value of a
+ parameter.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The elements that use this type designate either a relative
- path or an absolute path starting with a "/".
+ 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.
+ 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:complexType name="persistence-context-refType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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:
+ 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,
+ - 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 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
+ - optional injection targets
- Examples:
+ Examples:
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
<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"/>
+ 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>
+ 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">
+ type="javaee:string"
+ minOccurs="0">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="persistence-context-type"
- type="javaee:persistence-context-typeType"
- minOccurs="0"/>
+ type="javaee:persistence-context-typeType"
+ minOccurs="0"/>
<xsd:element name="persistence-property"
- type="javaee:propertyType"
- minOccurs="0"
- maxOccurs="unbounded">
+ type="javaee:propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:group ref="javaee:resourceGroup"/>
<xsd:annotation>
<xsd:documentation>
- The persistence-context-typeType specifies the transactional
- nature of a persistence context reference.
+ 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
+ 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:enumeration value="Transaction"/>
+ <xsd:enumeration value="Extended"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="persistence-unit-refType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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:
+ 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,
+ - 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
+ - optional injection targets
- Examples:
+ Examples:
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-name>
</persistence-unit-ref>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="javaee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ 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>
+ 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">
+ type="javaee:string"
+ minOccurs="0">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:group ref="javaee:resourceGroup"/>
<xsd:annotation>
<xsd:documentation>
- Specifies a name/value pair.
+ Specifies a name/value pair.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="name"
- type="javaee:xsdStringType">
+ type="javaee:xsdStringType">
</xsd:element>
<xsd:element name="value"
- type="javaee:xsdStringType">
+ type="javaee:xsdStringType">
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:complexType name="remoteType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- The remote element contains the fully-qualified name
- of the enterprise bean's remote interface.
+ The remote element contains the fully-qualified name
+ of the enterprise bean's remote interface.
- Example:
+ Example:
- <remote>com.wombat.empl.EmployeeService</remote>
+ <remote>com.wombat.empl.EmployeeService</remote>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<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 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:
+ The value must be one of the two following:
- Application
- Container
+ Application
+ Container
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="javaee:string">
- <xsd:enumeration value="Application"/>
- <xsd:enumeration value="Container"/>
+ <xsd:enumeration value="Application"/>
+ <xsd:enumeration value="Container"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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:
+ 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
+ Shareable
+ Unshareable
- The default value is Shareable.
+ 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: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>
-
- ]]>
+ <![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"/>
+ 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>
+ 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>
+ 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: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>
-
- ]]>
+ <![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"/>
+ 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>
+ 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>
+ 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"/>
+ type="javaee:res-authType"
+ minOccurs="0"/>
<xsd:element name="res-sharing-scope"
- type="javaee:res-sharing-scopeType"
- minOccurs="0"/>
+ type="javaee:res-sharing-scopeType"
+ minOccurs="0"/>
<xsd:group ref="javaee:resourceGroup"/>
<xsd:annotation>
<xsd:documentation>
- This group collects elements that are common to all the
- JNDI resource elements.
+ 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>
+ 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"/>
+ type="javaee:injection-targetType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
- The role-nameType designates the name of a security role.
+ The role-nameType designates the name of a security role.
- The name must conform to the lexical rules for a token.
+ The name must conform to the lexical rules for a token.
</xsd:documentation>
</xsd:annotation>
<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.
+ 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"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="javaee:role-nameType"/>
+ type="javaee:role-nameType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<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.
+ 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"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="javaee:role-nameType">
- <xsd:annotation>
- <xsd:documentation>
+ 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.
+ 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: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>
+ 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 name="security-roleType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![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.
+ 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:
+ 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>
+ <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"/>
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="javaee:role-nameType"/>
+ type="javaee:role-nameType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<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.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This simple type designates a boolean with only two
- permissible values
+ This simple type designates a boolean with only two
+ permissible values
- - true
- - false
+ - true
+ - false
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="javaee:xsdBooleanType">
- <xsd:pattern value="(true|false)"/>
+ <xsd:pattern value="(true|false)"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<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.
+ 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:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:anyURI.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:boolean.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:integer.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:NMTOKEN.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:nonNegativeInteger.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:positiveInteger.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:QName.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type adds an "id" attribute to xsd:string.
+ 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:attribute name="id" type="xsd:ID"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
java.lang.Long
java.lang.Float
java.lang.Double
- java.lang.Class
- any enumeration type (i.e. a subclass of java.lang.Enum)
+ java.lang.Class
+ any enumeration type (i.e. a subclass of java.lang.Enum)
Examples:
<xsd:annotation>
<xsd:documentation>
- The following transaction isolation levels are allowed
- (see documentation for the java.sql.Connection interface):
+ The following transaction isolation levels are allowed
+ (see documentation for the java.sql.Connection interface):
TRANSACTION_READ_UNCOMMITTED
TRANSACTION_READ_COMMITTED
TRANSACTION_REPEATABLE_READ
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/javaee"
- xmlns:javaee="http://java.sun.com/xml/ns/javaee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.2">
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.2">
<xsd:annotation>
<xsd:documentation>
- @(#)javaee_web_services_1_2.xsds 1.18 02/13/06
+ @(#)javaee_web_services_1_2.xsds 1.18 02/13/06
</xsd:documentation>
</xsd:annotation>
<xsd:documentation>
<![CDATA[
- The webservices element is the root element for the web services
- deployment descriptor. It specifies the set of web service
- descriptions that are to be deployed into the Java EE Application
- Server and the dependencies they have on container resources and
- services. The deployment descriptor must be named
- "META-INF/webservices.xml" in the web services' jar file.
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the Java EE Application
+ Server and the dependencies they have on container resources and
+ services. The deployment descriptor must be named
+ "META-INF/webservices.xml" in the web services' jar file.
- Used in: webservices.xml
+ Used in: webservices.xml
- All webservices deployment descriptors must indicate the
- webservices schema by using the Java EE namespace:
+ All webservices deployment descriptors must indicate the
+ webservices schema by using the Java EE namespace:
- http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee
- and by indicating the version of the schema by using the version
- element as shown below:
+ and by indicating the version of the schema by using the version
+ element as shown below:
- <webservices xmlns="http://java.sun.com/xml/ns/javaee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
- http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd"
- version="1.2">
- ...
- </webservices>
+ <webservices xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd"
+ version="1.2">
+ ...
+ </webservices>
- The instance documents may indicate the published version of the
- schema using the xsi:schemaLocation attribute for the Java EE
- namespace with the following location:
+ The instance documents may indicate the published version of the
+ schema using the xsi:schemaLocation attribute for the Java EE
+ namespace with the following location:
- http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd
+ http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
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.
+ 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:annotation>
<xsd:documentation>
- The webservices element is the root element for the web services
- deployment descriptor. It specifies the set of web service
- descriptions that are to be deployed into the Java EE Application Server
- and the dependencies they have on container resources and services.
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the Java EE Application Server
+ and the dependencies they have on container resources and services.
- Used in: webservices.xml
+ Used in: webservices.xml
</xsd:documentation>
</xsd:annotation>
<xsd:key name="webservice-description-name-key">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The webservice-description-name identifies the collection of
- port-components associated with a WSDL file and JAX-RPC mapping. The
- name must be unique within the deployment descriptor.
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC mapping. The
+ name must be unique within the deployment descriptor.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:webservice-description"/>
<xsd:field xpath="javaee:webservice-description-name"/>
<xsd:choice minOccurs="0" maxOccurs="1">
<xsd:element name="service-name-pattern"
- type="javaee:qname-pattern" />
+ type="javaee:qname-pattern" />
<xsd:element name="port-name-pattern"
- type="javaee:qname-pattern" />
+ type="javaee:qname-pattern" />
<xsd:element name="protocol-bindings"
- type="javaee:protocol-bindingListType"/>
+ type="javaee:protocol-bindingListType"/>
</xsd:choice>
<xsd:element name="handler"
type="javaee:port-component_handlerType"
- minOccurs="1" maxOccurs="unbounded"/>
+ minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:sequence>
<xsd:element name="handler-chain"
type="javaee:handler-chainType"
- minOccurs="0" maxOccurs="unbounded"/>
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The port-component element associates a WSDL port with a web service
- interface and implementation. It defines the name of the port as a
- component, optional description, optional display name, optional iconic
- representations, WSDL port QName, Service Endpoint Interface, Service
- Implementation Bean.
+ The port-component element associates a WSDL port with a web service
+ interface and implementation. It defines the name of the port as a
+ component, optional description, optional display name, optional iconic
+ representations, WSDL port QName, Service Endpoint Interface, Service
+ Implementation Bean.
- This element also associates a WSDL service with a JAX-WS Provider
- implementation.
+ This element also associates a WSDL service with a JAX-WS Provider
+ implementation.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="javaee:descriptionType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="display-name"
- type="javaee:display-nameType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="icon"
- type="javaee:iconType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:iconType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="port-component-name"
- type="javaee:string">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
-
- The port-component-name element specifies a port component's
- name. This name is assigned by the module producer to name
- the service implementation bean in the module's deployment
- descriptor. The name must be unique among the port component
- names defined in the same module.
-
- Used in: port-component
-
- Example:
- <port-component-name>EmployeeService
- </port-component-name>
-
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port component's
+ name. This name is assigned by the module producer to name
+ the service implementation bean in the module's deployment
+ descriptor. The name must be unique among the port component
+ names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+
<port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-service"
- type="javaee:xsdQNameType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name space and local name part of the WSDL
- service QName. This is required to be specified for
- port components that are JAX-WS Provider implementations.
+ Defines the name space and local name part of the WSDL
+ service QName. This is required to be specified for
+ port components that are JAX-WS Provider implementations.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-port"
- type="javaee:xsdQNameType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name space and local name part of the WSDL
- port QName. This is not required to be specified for port
- components that are JAX-WS Provider implementations
+ Defines the name space and local name part of the WSDL
+ port QName. This is not required to be specified for port
+ components that are JAX-WS Provider implementations
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="enable-mtom"
type="javaee:true-falseType"
- minOccurs="0" maxOccurs="1">
+ minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism for an
endpoint implementation.
- Not to be specified for JAX-RPC runtime
+ Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="protocol-binding"
type="javaee:protocol-bindingType"
- minOccurs="0" maxOccurs="1">
+ minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Used to specify the protocol binding used by the port-component.
- If this element is not specified, then the default binding is
+ If this element is not specified, then the default binding is
used (SOAP 1.1 over HTTP)
</xsd:documentation>
</xsd:element>
<xsd:element name="service-endpoint-interface"
- type="javaee:fully-qualified-classType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
+ type="javaee:fully-qualified-classType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
- The service-endpoint-interface element contains the
- fully-qualified name of the port component's Service Endpoint
- Interface.
+ The service-endpoint-interface element contains the
+ fully-qualified name of the port component's Service Endpoint
+ Interface.
- Used in: port-component
+ Used in: port-component
- Example:
- <remote>com.wombat.empl.EmployeeService</remote>
+ Example:
+ <remote>com.wombat.empl.EmployeeService</remote>
- This may not be specified in case there is no Service
- Enpoint Interface as is the case with directly using an
- implementation class with the @WebService annotation.
+ This may not be specified in case there is no Service
+ Enpoint Interface as is the case with directly using an
+ implementation class with the @WebService annotation.
- When the port component is a Provider implementation
- this is not specified.
+ When the port component is a Provider implementation
+ this is not specified.
- ]]>
- </xsd:documentation>
- </xsd:annotation>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-impl-bean"
- type="javaee:service-impl-beanType"/>
+ type="javaee:service-impl-beanType"/>
<xsd:choice>
- <xsd:element name="handler"
- type="javaee:port-component_handlerType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
- To be used with JAX-RPC based runtime only.
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="handler-chains"
- type="javaee:handler-chainsType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
- To be used with JAX-WS based runtime only.
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
+ <xsd:element name="handler"
+ type="javaee:port-component_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-RPC based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-chains"
+ type="javaee:handler-chainsType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-WS based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
</xsd:choice>
</xsd:sequence>
<xsd:annotation>
<xsd:documentation>
- Declares the handler for a port-component. Handlers can access the
- init-param name/value pairs using the HandlerInfo interface.
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface.
- Used in: port-component
+ Used in: port-component
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="javaee:descriptionGroup"/>
<xsd:element name="handler-name"
- type="javaee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name of the handler. The name must be unique within the
- module.
+ Defines the name of the handler. The name must be unique within the
+ module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="handler-class"
- type="javaee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines a fully qualified class name for the handler implementation.
+ Defines a fully qualified class name for the handler implementation.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="init-param"
- type="javaee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="soap-header"
- type="javaee:xsdQNameType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the QName of a SOAP header that will be processed by the
- handler.
+ Defines the QName of a SOAP header that will be processed by the
+ handler.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="soap-role"
- type="javaee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The soap-role element contains a SOAP actor definition that the
- Handler will play as a role.
+ The soap-role element contains a SOAP actor definition that the
+ Handler will play as a role.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:simpleType name="protocol-URIAliasType">
<xsd:annotation>
<xsd:documentation>
- Defines the type that is used for specifying tokens that
- start with ## which are used to alias existing standard
- protocol bindings and support aliases for new standard
- binding URIs that are introduced in future specifications.
+ Defines the type that is used for specifying tokens that
+ start with ## which are used to alias existing standard
+ protocol bindings and support aliases for new standard
+ binding URIs that are introduced in future specifications.
- The following tokens alias the standard protocol binding
- URIs:
+ The following tokens alias the standard protocol binding
+ URIs:
- ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
- ##SOAP11_HTTP_MTOM =
+ ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
+ ##SOAP11_HTTP_MTOM =
"http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
##SOAP12_HTTP_MTOM =
- "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
+ "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
</xsd:documentation>
<xsd:simpleType name="protocol-bindingListType">
<xsd:annotation>
<xsd:documentation>
- Defines the type used for specifying a list of
- protocol-bindingType(s). For e.g.
+ Defines the type used for specifying a list of
+ protocol-bindingType(s). For e.g.
- ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
+ ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType name="protocol-bindingType">
<xsd:annotation>
<xsd:documentation>
- Defines the type used for specifying the URI for the
- protocol binding used by the port-component. For
- portability one could use one of the following tokens that
- alias the standard binding types:
+ Defines the type used for specifying the URI for the
+ protocol binding used by the port-component. For
+ portability one could use one of the following tokens that
+ alias the standard binding types:
- ##SOAP11_HTTP
- ##SOAP11_HTTP_MTOM
- ##SOAP12_HTTP
- ##SOAP12_HTTP_MTOM
- ##XML_HTTP
+ ##SOAP11_HTTP
+ ##SOAP11_HTTP_MTOM
+ ##SOAP12_HTTP
+ ##SOAP12_HTTP_MTOM
+ ##XML_HTTP
- Other specifications could define tokens that start with ##
- to alias new standard binding URIs that are introduced.
+ Other specifications could define tokens that start with ##
+ to alias new standard binding URIs that are introduced.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType name="qname-pattern">
<xsd:annotation>
<xsd:documentation>
- This is used to specify the QName pattern in the
- attribute service-name-pattern and port-name-pattern in
- the handler-chain element
+ This is used to specify the QName pattern in the
+ attribute service-name-pattern and port-name-pattern in
+ the handler-chain element
- For example, the various forms acceptable here for
- service-name-pattern attribute in handler-chain element
- are :
+ For example, the various forms acceptable here for
+ service-name-pattern attribute in handler-chain element
+ are :
- Exact Name: service-name-pattern="ns1:EchoService"
+ Exact Name: service-name-pattern="ns1:EchoService"
- In this case, handlers specified in this
- handler-chain element will apply to all ports with
- this exact service name. The namespace prefix must
- have been declared in a namespace declaration
- attribute in either the start-tag of the element
- where the prefix is used or in an an ancestor
- element (i.e. an element in whose content the
- prefixed markup occurs)
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports with
+ this exact service name. The namespace prefix must
+ have been declared in a namespace declaration
+ attribute in either the start-tag of the element
+ where the prefix is used or in an an ancestor
+ element (i.e. an element in whose content the
+ prefixed markup occurs)
- Pattern : service-name-pattern="ns1:EchoService*"
+ Pattern : service-name-pattern="ns1:EchoService*"
- In this case, handlers specified in this
- handler-chain element will apply to all ports whose
- Service names are like EchoService1, EchoServiceFoo
- etc. The namespace prefix must have been declared in
- a namespace declaration attribute in either the
- start-tag of the element where the prefix is used or
- in an an ancestor element (i.e. an element in whose
- content the prefixed markup occurs)
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports whose
+ Service names are like EchoService1, EchoServiceFoo
+ etc. The namespace prefix must have been declared in
+ a namespace declaration attribute in either the
+ start-tag of the element where the prefix is used or
+ in an an ancestor element (i.e. an element in whose
+ content the prefixed markup occurs)
- Wild Card : service-name-pattern="*"
+ Wild Card : service-name-pattern="*"
- In this case, handlers specified in this handler-chain
- element will apply to ports of all service names.
+ In this case, handlers specified in this handler-chain
+ element will apply to ports of all service names.
- The same can be applied to port-name attribute in
- handler-chain element.
+ The same can be applied to port-name attribute in
+ handler-chain element.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The service-impl-bean element defines the web service implementation.
- A service implementation can be an EJB bean class or JAX-RPC web
- component. Existing EJB implementations are exposed as a web service
- using an ejb-link.
+ The service-impl-bean element defines the web service implementation.
+ A service implementation can be an EJB bean class or JAX-RPC web
+ component. Existing EJB implementations are exposed as a web service
+ using an ejb-link.
- Used in: port-component
+ Used in: port-component
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
<xsd:element name="ejb-link"
- type="javaee:ejb-linkType"/>
+ type="javaee:ejb-linkType"/>
<xsd:element name="servlet-link"
- type="javaee:servlet-linkType"/>
+ type="javaee:servlet-linkType"/>
</xsd:choice>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:complexType name="servlet-linkType">
<xsd:annotation>
<xsd:documentation>
- <![CDATA[
+ <![CDATA[
- The servlet-link element is used in the service-impl-bean element
- to specify that a Service Implementation Bean is defined as a
- JAX-RPC Service Endpoint.
+ The servlet-link element is used in the service-impl-bean element
+ to specify that a Service Implementation Bean is defined as a
+ JAX-RPC Service Endpoint.
- The value of the servlet-link element must be the servlet-name of
- a JAX-RPC Service Endpoint in the same WAR file.
+ The value of the servlet-link element must be the servlet-name of
+ a JAX-RPC Service Endpoint in the same WAR file.
- Used in: service-impl-bean
+ Used in: service-impl-bean
- Example:
- <servlet-link>StockQuoteService</servlet-link>
+ Example:
+ <servlet-link>StockQuoteService</servlet-link>
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:annotation>
<xsd:documentation>
- The webservice-description element defines a WSDL document file
- and the set of Port components associated with the WSDL ports
- defined in the WSDL document. There may be multiple
- webservice-descriptions defined within a module.
+ The webservice-description element defines a WSDL document file
+ and the set of Port components associated with the WSDL ports
+ defined in the WSDL document. There may be multiple
+ webservice-descriptions defined within a module.
- All WSDL file ports must have a corresponding port-component element
- defined.
+ All WSDL file ports must have a corresponding port-component element
+ defined.
- Used in: webservices
+ Used in: webservices
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="javaee:descriptionType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="display-name"
- type="javaee:display-nameType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="icon"
- type="javaee:iconType"
- minOccurs="0" maxOccurs="1"/>
+ type="javaee:iconType"
+ minOccurs="0" maxOccurs="1"/>
<xsd:element name="webservice-description-name"
- type="javaee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- The webservice-description-name identifies the collection of
- port-components associated with a WSDL file and JAX-RPC
- mapping. The name must be unique within the deployment descriptor.
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC
+ mapping. The name must be unique within the deployment descriptor.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-file"
- type="javaee:pathType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The wsdl-file element contains the name of a WSDL file in the
- module. The file name is a relative path within the module.
+ The wsdl-file element contains the name of a WSDL file in the
+ module. The file name is a relative path within the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="jaxrpc-mapping-file"
- type="javaee:pathType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The jaxrpc-mapping-file element contains the name of a file that
- describes the JAX-RPC mapping between the Java interaces used by
- the application and the WSDL description in the wsdl-file. The
- file name is a relative path within the module.
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module.
- This is not required when JAX-WS based runtime is used.
+ This is not required when JAX-WS based runtime is used.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-component"
- type="javaee:port-componentType"
- minOccurs="1" maxOccurs="unbounded">
- <xsd:key name="port-component_handler-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- Defines the name of the handler. The name must be unique
- within the module.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="javaee:handler"/>
- <xsd:field xpath="javaee:handler-name"/>
- </xsd:key>
+ type="javaee:port-componentType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:handler"/>
+ <xsd:field xpath="javaee:handler-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:sequence>
<xsd:group ref="javaee:descriptionGroup"/>
<xsd:element name="webservice-description"
- type="javaee:webservice-descriptionType"
- minOccurs="1" maxOccurs="unbounded">
- <xsd:key name="port-component-name-key">
- <xsd:annotation>
- <xsd:documentation>
- <![CDATA[
-
- The port-component-name element specifies a port
- component's name. This name is assigned by the module
- producer to name the service implementation bean in the
- module's deployment descriptor. The name must be unique
- among the port component names defined in the same module.
-
- Used in: port-component
-
- Example:
- <port-component-name>EmployeeService
- </port-component-name>
-
- ]]>
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="javaee:port-component"/>
- <xsd:field xpath="javaee:port-component-name"/>
- </xsd:key>
+ type="javaee:webservice-descriptionType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port
+ component's name. This name is assigned by the module
+ producer to name the service implementation bean in the
+ module's deployment descriptor. The name must be unique
+ among the port component names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+
<port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:port-component"/>
+ <xsd:field xpath="javaee:port-component-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="version"
- type="javaee:dewey-versionType"
- fixed="1.2"
- use="required">
+ type="javaee:dewey-versionType"
+ fixed="1.2"
+ use="required">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The required value for the version is 1.2.
+ The required value for the version is 1.2.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<webservices xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
- http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.xsd"
+ http://java.sun.com/xml/ns/javaee/javaee_web_services_1_3.xsd"
version="1.3">
...
</webservices>
Used in: port-component
Example:
- <port-component-name>EmployeeService
- </port-component-name>
+
<port-component-name>EmployeeService
+ </port-component-name>
]]>
</xsd:documentation>
Used in: port-component
Example:
- <remote>com.wombat.empl.EmployeeService</remote>
+ <remote>com.wombat.empl.EmployeeService</remote>
This may not be specified in case there is no Service
Enpoint Interface as is the case with directly using an
<xsd:annotation>
<xsd:documentation>
- To be used with JAX-RPC based runtime only.
+ To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- To be used with JAX-WS based runtime only.
+ To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
Used in: service-impl-bean
Example:
- <servlet-link>StockQuoteService</servlet-link>
+ <servlet-link>StockQuoteService</servlet-link>
]]>
</xsd:documentation>
<xsd:annotation>
<xsd:documentation>
<![CDATA[[
- The port-component-name element specifies a port
- component's name. This name is assigned by the module
- producer to name the service implementation bean in the
- module's deployment descriptor. The name must be unique
- among the port component names defined in the same module.
+ The port-component-name element specifies a port
+ component's name. This name is assigned by the module
+ producer to name the service implementation bean in the
+ module's deployment descriptor. The name must be unique
+ among the port component names defined in the same module.
- Used in: port-component
+ Used in: port-component
- Example:
-
<port-component-name>EmployeeService
- </port-component-name>
+ Example:
+ <port-component-name>EmployeeService
+ </port-component-name>
-
+
]]>
</xsd:documentation>
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/javaee"
- xmlns:javaee="http://java.sun.com/xml/ns/javaee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="1.2">
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.2">
<xsd:annotation>
<xsd:documentation>
- @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
+ @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The port-component-ref element declares a client dependency
- on the container for resolving a Service Endpoint Interface
- to a WSDL port. It optionally associates the Service Endpoint
- Interface with a particular port-component. This is only used
- by the container for a Service.getPort(Class) method call.
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="service-endpoint-interface"
- type="javaee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-endpoint-interface element defines a fully qualified
- Java class that represents the Service Endpoint Interface of a
- WSDL port.
+ The service-endpoint-interface element defines a fully qualified
+ Java class that represents the Service Endpoint Interface of a
+ WSDL port.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="enable-mtom"
type="javaee:true-falseType"
- minOccurs="0" maxOccurs="1">
+ minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
- side for a port-component.
+ side for a port-component.
- Not to be specified for JAX-RPC runtime
+ Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="port-component-link"
- type="javaee:string"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
-
- The port-component-link element links a port-component-ref
- to a specific port-component required to be made available
- by a service reference.
-
- The value of a port-component-link must be the
- port-component-name of a port-component in the same module
- or another module in the same application unit. The syntax
- for specification follows the syntax defined for ejb-link
- in the EJB 2.0 specification.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="javaee:string"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-link element links a port-component-ref
+ to a specific port-component required to be made available
+ by a service reference.
+
+ The value of a port-component-link must be the
+ port-component-name of a port-component in the same module
+ or another module in the same application unit. The syntax
+ for specification follows the syntax defined for ejb-link
+ in the EJB 2.0 specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:group name="service-refGroup">
<xsd:sequence>
<xsd:element name="service-ref"
- type="javaee:service-refType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:key name="service-ref_handler-name-key">
- <xsd:annotation>
- <xsd:documentation>
-
- Defines the name of the handler. The name must be unique
- within the module.
-
- </xsd:documentation>
- </xsd:annotation>
- <xsd:selector xpath="javaee:handler"/>
- <xsd:field xpath="javaee:handler-name"/>
- </xsd:key>
+ type="javaee:service-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:key name="service-ref_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:handler"/>
+ <xsd:field xpath="javaee:handler-name"/>
+ </xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
- The service-ref element declares a reference to a Web
- service. It contains optional description, display name and
- icons, a declaration of the required Service interface,
- an optional WSDL document location, an optional set
- of JAX-RPC mappings, an optional QName for the service element,
- an optional set of Service Endpoint Interfaces to be resolved
- by the container to a WSDL port, and an optional set of handlers.
+ The service-ref element declares a reference to a Web
+ service. It contains optional description, display name and
+ icons, a declaration of the required Service interface,
+ an optional WSDL document location, an optional set
+ of JAX-RPC mappings, an optional QName for the service element,
+ an optional set of Service Endpoint Interfaces to be resolved
+ by the container to a WSDL port, and an optional set of handlers.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="javaee:descriptionGroup"/>
<xsd:element name="service-ref-name"
- type="javaee:jndi-nameType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-ref-name element declares logical name that the
- components in the module use to look up the Web service. It
- is recommended that all service reference names start with
- "service/".
+ The service-ref-name element declares logical name that the
+ components in the module use to look up the Web service. It
+ is recommended that all service reference names start with
+ "service/".
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-interface"
- type="javaee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-interface element declares the fully qualified class
- name of the JAX-RPC Service interface the client depends on.
- In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
- generated Service Interface class may also be specified.
+ The service-interface element declares the fully qualified class
+ name of the JAX-RPC Service interface the client depends on.
+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
+ generated Service Interface class may also be specified.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-ref-type"
- type="javaee:fully-qualified-classType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
-
- The service-ref-type element declares the type of the service-ref
- element that is injected or returned when a JNDI lookup is done.
- This must be either a fully qualified name of Service class or
- the fully qualified name of service endpoint interface class.
- This is only used with JAX-WS runtime where the corresponding
- @WebServiceRef annotation can be used to denote both a Service
- or a Port.
-
- If this is not specified, then the type of service-ref element
- that is injected or returned when a JNDI lookup is done is
- always a Service interface/class.
- </xsd:documentation>
- </xsd:annotation>
+ type="javaee:fully-qualified-classType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref-type element declares the type of the service-ref
+ element that is injected or returned when a JNDI lookup is done.
+ This must be either a fully qualified name of Service class or
+ the fully qualified name of service endpoint interface class.
+ This is only used with JAX-WS runtime where the corresponding
+ @WebServiceRef annotation can be used to denote both a Service
+ or a Port.
+
+ If this is not specified, then the type of service-ref element
+ that is injected or returned when a JNDI lookup is done is
+ always a Service interface/class.
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="wsdl-file"
- type="javaee:xsdAnyURIType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdAnyURIType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The wsdl-file element contains the URI location of a WSDL
- file. The location is relative to the root of the module.
+ The wsdl-file element contains the URI location of a WSDL
+ file. The location is relative to the root of the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="jaxrpc-mapping-file"
- type="javaee:pathType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The jaxrpc-mapping-file element contains the name of a file that
- describes the JAX-RPC mapping between the Java interaces used by
- the application and the WSDL description in the wsdl-file. The
- file name is a relative path within the module file.
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module file.
- This is not required when JAX-WS based runtime is used.
+ This is not required when JAX-WS based runtime is used.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="service-qname"
- type="javaee:xsdQNameType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
- The service-qname element declares the specific WSDL service
- element that is being refered to. It is not specified if no
- wsdl-file is declared.
+ The service-qname element declares the specific WSDL service
+ element that is being refered to. It is not specified if no
+ wsdl-file is declared.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-component-ref"
- type="javaee:port-component-refType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- The port-component-ref element declares a client dependency
- on the container for resolving a Service Endpoint Interface
- to a WSDL port. It optionally associates the Service Endpoint
- Interface with a particular port-component. This is only used
- by the container for a Service.getPort(Class) method call.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="javaee:port-component-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:choice>
- <xsd:element name="handler"
- type="javaee:service-ref_handlerType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
-
- Declares the handler for a port-component. Handlers can
- access the init-param name/value pairs using the
- HandlerInfo interface. If port-name is not specified, the
- handler is assumed to be associated with all ports of the
- service.
-
- To be used with JAX-RPC based runtime only.
-
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
- <xsd:element name="handler-chains"
- type="javaee:service-ref_handler-chainsType"
- minOccurs="0" maxOccurs="1">
- <xsd:annotation>
- <xsd:documentation>
- To be used with JAX-WS based runtime only.
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
+ <xsd:element name="handler"
+ type="javaee:service-ref_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can
+ access the init-param name/value pairs using the
+ HandlerInfo interface. If port-name is not specified, the
+ handler is assumed to be associated with all ports of the
+ service.
+
+ To be used with JAX-RPC based runtime only.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-chains"
+ type="javaee:service-ref_handler-chainsType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-WS based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
</xsd:choice>
<xsd:group ref="javaee:resourceGroup"/>
<xsd:choice minOccurs="0" maxOccurs="1">
<xsd:element name="service-name-pattern"
- type="javaee:service-ref_qname-pattern" />
+ type="javaee:service-ref_qname-pattern" />
<xsd:element name="port-name-pattern"
- type="javaee:service-ref_qname-pattern" />
+ type="javaee:service-ref_qname-pattern" />
<xsd:element name="protocol-bindings"
- type="javaee:service-ref_protocol-bindingListType"/>
+ type="javaee:service-ref_protocol-bindingListType"/>
</xsd:choice>
<xsd:element name="handler"
type="javaee:service-ref_handlerType"
- minOccurs="1" maxOccurs="unbounded"/>
+ minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:sequence>
<xsd:element name="handler-chain"
type="javaee:service-ref_handler-chainType"
- minOccurs="0" maxOccurs="unbounded"/>
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- Declares the handler for a port-component. Handlers can access the
- init-param name/value pairs using the HandlerInfo interface. If
- port-name is not specified, the handler is assumed to be associated
- with all ports of the service.
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface. If
+ port-name is not specified, the handler is assumed to be associated
+ with all ports of the service.
- Used in: service-ref
+ Used in: service-ref
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="javaee:descriptionGroup"/>
<xsd:element name="handler-name"
- type="javaee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the name of the handler. The name must be unique
- within the module.
+ Defines the name of the handler. The name must be unique
+ within the module.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="handler-class"
- type="javaee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines a fully qualified class name for the handler
- implementation.
+ Defines a fully qualified class name for the handler
+ implementation.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="init-param"
- type="javaee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="soap-header"
- type="javaee:xsdQNameType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- Defines the QName of a SOAP header that will be processed
- by the handler.
+ Defines the QName of a SOAP header that will be processed
+ by the handler.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="soap-role"
- type="javaee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The soap-role element contains a SOAP actor definition that
- the Handler will play as a role.
+ The soap-role element contains a SOAP actor definition that
+ the Handler will play as a role.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="port-name"
- type="javaee:string"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The port-name element defines the WSDL port-name that a
- handler should be associated with.
+ The port-name element defines the WSDL port-name that a
+ handler should be associated with.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:simpleType name="service-ref_protocol-URIAliasType">
<xsd:annotation>
<xsd:documentation>
- Defines the type that is used for specifying tokens that
- start with ## which are used to alias existing standard
- protocol bindings and support aliases for new standard
- binding URIs that are introduced in future specifications.
+ Defines the type that is used for specifying tokens that
+ start with ## which are used to alias existing standard
+ protocol bindings and support aliases for new standard
+ binding URIs that are introduced in future specifications.
- The following tokens alias the standard protocol binding
- URIs:
+ The following tokens alias the standard protocol binding
+ URIs:
- ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
- ##SOAP11_HTTP_MTOM =
+ ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
+ ##SOAP11_HTTP_MTOM =
"http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
##SOAP12_HTTP_MTOM =
<xsd:simpleType name="service-ref_protocol-bindingListType">
<xsd:annotation>
<xsd:documentation>
- Defines the type used for specifying a list of
- protocol-bindingType(s). For e.g.
+ Defines the type used for specifying a list of
+ protocol-bindingType(s). For e.g.
- ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
+ ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType name="service-ref_protocol-bindingType">
<xsd:annotation>
<xsd:documentation>
- Defines the type used for specifying the URI for the
- protocol binding used by the port-component. For
- portability one could use one of the following tokens that
- alias the standard binding types:
+ Defines the type used for specifying the URI for the
+ protocol binding used by the port-component. For
+ portability one could use one of the following tokens that
+ alias the standard binding types:
- ##SOAP11_HTTP
- ##SOAP11_HTTP_MTOM
+ ##SOAP11_HTTP
+ ##SOAP11_HTTP_MTOM
##SOAP12_HTTP
##SOAP12_HTTP_MTOM
##XML_HTTP
- Other specifications could define tokens that start with ##
- to alias new standard binding URIs that are introduced.
+ Other specifications could define tokens that start with ##
+ to alias new standard binding URIs that are introduced.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType name="service-ref_qname-pattern">
<xsd:annotation>
<xsd:documentation>
- This is used to specify the QName pattern in the
- attribute service-name-pattern and port-name-pattern in
- the handler-chain element
-
- For example, the various forms acceptable here for
- service-name-pattern attribute in handler-chain element
- are :
-
- Exact Name: service-name-pattern="ns1:EchoService"
-
- In this case, handlers specified in this
- handler-chain element will apply to all ports with
- this exact service name. The namespace prefix must
- have been declared in a namespace declaration
- attribute in either the start-tag of the element
- where the prefix is used or in an an ancestor
- element (i.e. an element in whose content the
- prefixed markup occurs)
-
- Pattern : service-name-pattern="ns1:EchoService*"
-
- In this case, handlers specified in this
- handler-chain element will apply to all ports whose
- Service names are like EchoService1, EchoServiceFoo
- etc. The namespace prefix must have been declared in
- a namespace declaration attribute in either the
- start-tag of the element where the prefix is used or
- in an an ancestor element (i.e. an element in whose
- content the prefixed markup occurs)
-
- Wild Card : service-name-pattern="*"
-
- In this case, handlers specified in this handler-chain
- element will apply to ports of all service names.
-
- The same can be applied to port-name attribute in
- handler-chain element.
+ This is used to specify the QName pattern in the
+ attribute service-name-pattern and port-name-pattern in
+ the handler-chain element
+
+ For example, the various forms acceptable here for
+ service-name-pattern attribute in handler-chain element
+ are :
+
+ Exact Name: service-name-pattern="ns1:EchoService"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports with
+ this exact service name. The namespace prefix must
+ have been declared in a namespace declaration
+ attribute in either the start-tag of the element
+ where the prefix is used or in an an ancestor
+ element (i.e. an element in whose content the
+ prefixed markup occurs)
+
+ Pattern : service-name-pattern="ns1:EchoService*"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports whose
+ Service names are like EchoService1, EchoServiceFoo
+ etc. The namespace prefix must have been declared in
+ a namespace declaration attribute in either the
+ start-tag of the element where the prefix is used or
+ in an an ancestor element (i.e. an element in whose
+ content the prefixed markup occurs)
+
+ Wild Card : service-name-pattern="*"
+
+ In this case, handlers specified in this handler-chain
+ element will apply to ports of all service names.
+
+ The same can be applied to port-name attribute in
+ handler-chain element.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- Declares the handler for a port-component. Handlers can
- access the init-param name/value pairs using the
- HandlerInfo interface. If port-name is not specified, the
- handler is assumed to be associated with all ports of the
- service.
+ Declares the handler for a port-component. Handlers can
+ access the init-param name/value pairs using the
+ HandlerInfo interface. If port-name is not specified, the
+ handler is assumed to be associated with all ports of the
+ service.
- To be used with JAX-RPC based runtime only.
+ To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- To be used with JAX-WS based runtime only.
+ To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
Exact Name: service-name-pattern="ns1:EchoService"
- In this case, handlers specified in this
- handler-chain element will apply to all ports with
- this exact service name. The namespace prefix must
- have been declared in a namespace declaration
- attribute in either the start-tag of the element
- where the prefix is used or in an an ancestor
- element (i.e. an element in whose content the
- prefixed markup occurs)
-
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports with
+ this exact service name. The namespace prefix must
+ have been declared in a namespace declaration
+ attribute in either the start-tag of the element
+ where the prefix is used or in an an ancestor
+ element (i.e. an element in whose content the
+ prefixed markup occurs)
+
Pattern : service-name-pattern="ns1:EchoService*"
- In this case, handlers specified in this
- handler-chain element will apply to all ports whose
- Service names are like EchoService1, EchoServiceFoo
- etc. The namespace prefix must have been declared in
- a namespace declaration attribute in either the
- start-tag of the element where the prefix is used or
- in an an ancestor element (i.e. an element in whose
- content the prefixed markup occurs)
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports whose
+ Service names are like EchoService1, EchoServiceFoo
+ etc. The namespace prefix must have been declared in
+ a namespace declaration attribute in either the
+ start-tag of the element where the prefix is used or
+ in an an ancestor element (i.e. an element in whose
+ content the prefixed markup occurs)
Wild Card : service-name-pattern="*"
- In this case, handlers specified in this handler-chain
- element will apply to ports of all service names.
+ In this case, handlers specified in this handler-chain
+ element will apply to ports of all service names.
The same can be applied to port-name attribute in
handler-chain element.
of the following form:
<!DOCTYPE web-app PUBLIC
- "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
- "http://java.sun.com/dtd/web-app_2_3.dtd">
+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
-->
Examples:
- <ejb-link>EmployeeRecord</ejb-link>
+ <ejb-link>EmployeeRecord</ejb-link>
- <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
-->
<!ELEMENT ejb-link (#PCDATA)>
The ejb-local-ref element is used for the declaration of a reference to
an enterprise bean's local home. The declaration consists of:
- - an optional description
- - the EJB reference name used in the code of the web application
- that's referencing the enterprise bean
- - the expected type of the referenced enterprise bean
- - the expected local home and local interfaces of the referenced
- enterprise bean
- - optional ejb-link information, used to specify the referenced
- enterprise bean
+ - an optional description
+ - the EJB reference name used in the code of the web application
+ that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected local home and local interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
Used in: web-app
-->
<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type,
- local-home, local, ejb-link?)>
+ local-home, local, ejb-link?)>
<!--
The ejb-ref element is used for the declaration of a reference to
an enterprise bean's home. The declaration consists of:
- - an optional description
- - the EJB reference name used in the code of
- the web application that's referencing the enterprise bean
- - the expected type of the referenced enterprise bean
- - the expected home and remote interfaces of the referenced
- enterprise bean
- - optional ejb-link information, used to specify the referenced
- enterprise bean
+ - an optional description
+ - the EJB reference name used in the code of
+ the web application that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
Used in: web-app
-->
<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
- home, remote, ejb-link?)>
+ home, remote, ejb-link?)>
<!--
The ejb-ref-name element contains the name of an EJB reference. The
The ejb-ref-type element must be one of the following:
- <ejb-ref-type>Entity</ejb-ref-type>
- <ejb-ref-type>Session</ejb-ref-type>
+ <ejb-ref-type>Entity</ejb-ref-type>
+ <ejb-ref-type>Session</ejb-ref-type>
Used in: ejb-local-ref, ejb-ref
-->
The following are the legal values of env-entry-type:
- java.lang.Boolean
- java.lang.Byte
- java.lang.Character
- java.lang.String
- java.lang.Short
- java.lang.Integer
- java.lang.Long
- java.lang.Float
- java.lang.Double
+ java.lang.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
Used in: env-entry
-->
The value of this element must be one of the two following:
- <res-auth>Application</res-auth>
- <res-auth>Container</res-auth>
+ <res-auth>Application</res-auth>
+ <res-auth>Container</res-auth>
Used in: resource-ref
-->
shared. The value of this element, if specified, must be one of the
two following:
- <res-sharing-scope>Shareable</res-sharing-scope>
- <res-sharing-scope>Unshareable</res-sharing-scope>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ <res-sharing-scope>Unshareable</res-sharing-scope>
The default value is Shareable.
</resource-env-ref>
-->
<!ELEMENT resource-env-ref (description?, resource-env-ref-name,
- resource-env-ref-type)>
+ resource-env-ref-type)>
<!--
The resource-env-ref-name element specifies the name of a resource
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>
+ <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>
-->
<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
- res-sharing-scope?)>
+ res-sharing-scope?)>
<!--
The role-link element is a reference to a defined security role. The
Example:
<security-role>
- <description>
- This role includes all employees who are authorized
- to access the employee service application.
- </description>
- <role-name>employee</role-name>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
</security-role>
-->
<!ELEMENT security-role (description?, role-name)>
limitations under the License.
-->
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
- targetNamespace="http://java.sun.com/xml/ns/j2ee"
- xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema"
- elementFormDefault="qualified"
- attributeFormDefault="unqualified"
- version="2.4">
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.4">
<xsd:annotation>
<xsd:documentation>
%W% %E%
<xsd:documentation>
<![CDATA[
- This is the XML Schema for the Servlet 2.4 deployment descriptor.
- The deployment descriptor must be named "WEB-INF/web.xml" in the
- web application's war file. All Servlet deployment descriptors
- must indicate the web application schema by using the J2EE
- namespace:
+ This is the XML Schema for the Servlet 2.4 deployment descriptor.
+ The deployment descriptor must be named "WEB-INF/web.xml" in the
+ web application's war file. All Servlet deployment descriptors
+ must indicate the web application schema by using the J2EE
+ namespace:
- http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee
- and by indicating the version of the schema by
- using the version element as shown below:
+ and by indicating the version of the schema by
+ using the version element as shown below:
- <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="..."
- version="2.4">
- ...
- </web-app>
+ <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="..."
+ version="2.4">
+ ...
+ </web-app>
- The instance documents may indicate the published version of
- the schema using the xsi:schemaLocation attribute for J2EE
- namespace with the following location:
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
- http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
- ]]>
+ ]]>
</xsd:documentation>
</xsd:annotation>
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.
+ 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:annotation>
<xsd:documentation>
- The web-app element is the root of the deployment
- descriptor for a web application. Note that the sub-elements
- of this element can be in the arbitrary order. Because of
- that, the multiplicity of the elements of distributable,
- session-config, welcome-file-list, jsp-config, login-config,
- and locale-encoding-mapping-list was changed from "?" to "*"
- in this schema. However, the deployment descriptor instance
- file must not contain multiple elements of session-config,
- jsp-config, and login-config. When there are multiple elements of
- welcome-file-list or locale-encoding-mapping-list, the container
- must concatenate the element contents. The multiple occurrence
- of the element distributable is redundant and the container
- treats that case exactly in the same way when there is only
- one distributable.
+ The web-app element is the root of the deployment
+ descriptor for a web application. Note that the sub-elements
+ of this element can be in the arbitrary order. Because of
+ that, the multiplicity of the elements of distributable,
+ session-config, welcome-file-list, jsp-config, login-config,
+ and locale-encoding-mapping-list was changed from "?" to "*"
+ in this schema. However, the deployment descriptor instance
+ file must not contain multiple elements of session-config,
+ jsp-config, and login-config. When there are multiple elements of
+ welcome-file-list or locale-encoding-mapping-list, the container
+ must concatenate the element contents. The multiple occurrence
+ of the element distributable is redundant and the container
+ treats that case exactly in the same way when there is only
+ one distributable.
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="web-app-servlet-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The servlet element contains the name of a servlet.
- The name must be unique within the web application.
+ The servlet element contains the name of a servlet.
+ The name must be unique within the web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:servlet"/>
<xsd:field xpath="j2ee:servlet-name"/>
<xsd:unique name="web-app-filter-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The filter element contains the name of a filter.
- The name must be unique within the web application.
+ The filter element contains the name of a filter.
+ The name must be unique within the web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:filter"/>
<xsd:field xpath="j2ee:filter-name"/>
<xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The ejb-local-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the web
- application's environment and is relative to the
- java:comp/env context. The name must be unique within
- the web application.
+ The ejb-local-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
- It is recommended that name is prefixed with "ejb/".
+ It is recommended that name is prefixed with "ejb/".
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:ejb-local-ref"/>
<xsd:field xpath="j2ee:ejb-ref-name"/>
<xsd:unique name="web-app-ejb-ref-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The ejb-ref-name element contains the name of an EJB
- reference. The EJB reference is an entry in the web
- application's environment and is relative to the
- java:comp/env context. The name must be unique within
- the web application.
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
- It is recommended that name is prefixed with "ejb/".
+ It is recommended that name is prefixed with "ejb/".
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:ejb-ref"/>
<xsd:field xpath="j2ee:ejb-ref-name"/>
<xsd:unique name="web-app-resource-env-ref-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The resource-env-ref-name element specifies the name of
- a resource environment reference; its value is the
- environment entry name used in the web application code.
- The name is a JNDI name relative to the java:comp/env
- context and must be unique within a web application.
+ The resource-env-ref-name element specifies the name of
+ a resource environment reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:resource-env-ref"/>
<xsd:field xpath="j2ee:resource-env-ref-name"/>
<xsd:unique name="web-app-message-destination-ref-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The message-destination-ref-name element specifies the name of
- a message destination reference; its value is the
- environment entry name used in the web application code.
- The name is a JNDI name relative to the java:comp/env
- context and must be unique within a web application.
+ The message-destination-ref-name element specifies the name of
+ a message destination reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:message-destination-ref"/>
<xsd:field xpath="j2ee:message-destination-ref-name"/>
<xsd:unique name="web-app-res-ref-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The res-ref-name element specifies the name of a
- resource manager connection factory reference. The name
- is a JNDI name relative to the java:comp/env context.
- The name must be unique within a web application.
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within a web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:resource-ref"/>
<xsd:field xpath="j2ee:res-ref-name"/>
<xsd:unique name="web-app-env-entry-name-uniqueness">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The env-entry-name element contains the name of a web
- application's environment entry. The name is a JNDI
- name relative to the java:comp/env context. The name
- must be unique within a web application.
+ The env-entry-name element contains the name of a web
+ application's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The name
+ must be unique within a web application.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:env-entry"/>
<xsd:key name="web-app-role-name-key">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- A role-name-key is specified to allow the references
- from the security-role-refs.
+ A role-name-key is specified to allow the references
+ from the security-role-refs.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:security-role"/>
<xsd:field xpath="j2ee:role-name"/>
</xsd:key>
<xsd:keyref name="web-app-role-name-references"
- refer="j2ee:web-app-role-name-key">
+ refer="j2ee:web-app-role-name-key">
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The keyref indicates the references from
- security-role-ref to a specified role-name.
+ The keyref indicates the references from
+ security-role-ref to a specified role-name.
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="j2ee:servlet/j2ee:security-role-ref"/>
<xsd:field xpath="j2ee:role-link"/>
<xsd:annotation>
<xsd:documentation>
- The auth-constraintType indicates the user roles that
- should be permitted access to this resource
- collection. The role-name used here must either correspond
- to the role-name of one of the security-role elements
- defined for this web application, or be the specially
- reserved role-name "*" that is a compact syntax for
- indicating all roles in the web application. If both "*"
- and rolenames appear, the container interprets this as all
- roles. If no roles are defined, no user is allowed access
- to the portion of the web application described by the
- containing security-constraint. The container matches
- role names case sensitively when determining access.
+ The auth-constraintType indicates the user roles that
+ should be permitted access to this resource
+ collection. The role-name used here must either correspond
+ to the role-name of one of the security-role elements
+ defined for this web application, or be the specially
+ reserved role-name "*" that is a compact syntax for
+ indicating all roles in the web application. If both "*"
+ and rolenames appear, the container interprets this as all
+ roles. If no roles are defined, no user is allowed access
+ to the portion of the web application described by the
+ containing security-constraint. The container matches
+ role names case sensitively when determining access.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="role-name"
- type="j2ee:role-nameType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:role-nameType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The auth-methodType is used to configure the authentication
- mechanism for the web application. As a prerequisite to
- gaining access to any web resources which are protected by
- an authorization constraint, a user must have authenticated
- using the configured mechanism. Legal values are "BASIC",
- "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
- authentication scheme.
+ The auth-methodType is used to configure the authentication
+ mechanism for the web application. As a prerequisite to
+ gaining access to any web resources which are protected by
+ an authorization constraint, a user must have authenticated
+ using the configured mechanism. Legal values are "BASIC",
+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
+ authentication scheme.
- Used in: login-config
+ Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
- and ERROR. A value of FORWARD means the Filter will be applied
- under RequestDispatcher.forward() calls. A value of REQUEST
- means the Filter will be applied under ordinary client calls to
- the path or servlet. A value of INCLUDE means the Filter will be
- applied under RequestDispatcher.include() calls. A value of
- ERROR means the Filter will be applied under the error page
- mechanism. The absence of any dispatcher elements in a
- filter-mapping indicates a default of applying filters only under
- ordinary client calls to the path or servlet.
+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
+ and ERROR. A value of FORWARD means the Filter will be applied
+ under RequestDispatcher.forward() calls. A value of REQUEST
+ means the Filter will be applied under ordinary client calls to
+ the path or servlet. A value of INCLUDE means the Filter will be
+ applied under RequestDispatcher.include() calls. A value of
+ ERROR means the Filter will be applied under the error page
+ mechanism. The absence of any dispatcher elements in a
+ filter-mapping indicates a default of applying filters only under
+ ordinary client calls to the path or servlet.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="FORWARD"/>
- <xsd:enumeration value="INCLUDE"/>
- <xsd:enumeration value="REQUEST"/>
- <xsd:enumeration value="ERROR"/>
+ <xsd:enumeration value="FORWARD"/>
+ <xsd:enumeration value="INCLUDE"/>
+ <xsd:enumeration value="REQUEST"/>
+ <xsd:enumeration value="ERROR"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The encodingType defines IANA character sets.
+ The encodingType defines IANA character sets.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The error-code contains an HTTP error code, ex: 404
+ The error-code contains an HTTP error code, ex: 404
- Used in: error-page
+ Used in: error-page
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:xsdPositiveIntegerType">
- <xsd:pattern value="\d{3}"/>
- <xsd:attribute name="id" type="xsd:ID"/>
+ <xsd:pattern value="\d{3}"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The error-pageType contains a mapping between an error code
- or exception type to the path of a resource in the web
- application.
+ The error-pageType contains a mapping between an error code
+ or exception type to the path of a resource in the web
+ application.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
- <xsd:element name="error-code"
- type="j2ee:error-codeType"/>
+ <xsd:element name="error-code"
+ type="j2ee:error-codeType"/>
- <xsd:element name="exception-type"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ <xsd:element name="exception-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The exception-type contains a fully qualified class
- name of a Java exception type.
+ The exception-type contains a fully qualified class
+ name of a Java exception type.
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
</xsd:choice>
<xsd:element name="location"
- type="j2ee:war-pathType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
- The location element contains the location of the
- resource in the web application relative to the root of
- the web application. The value of the location must have
- a leading `/'.
+ The location element contains the location of the
+ resource in the web application relative to the root of
+ the web application. The value of the location must have
+ a leading `/'.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- Declaration of the filter mappings in this web
- application is done by using filter-mappingType.
- The container uses the filter-mapping
- declarations to decide which filters to apply to a request,
- and in what order. The container matches the request URI to
- a Servlet in the normal way. To determine which filters to
- apply it matches filter-mapping declarations either on
- servlet-name, or on url-pattern for each filter-mapping
- element, depending on which style is used. The order in
- which filters are invoked is the order in which
- filter-mapping declarations that match a request URI for a
- servlet appear in the list of filter-mapping elements. The
- filter-name value must be the value of the filter-name
- sub-elements of one of the filter declarations in the
- deployment descriptor.
+ Declaration of the filter mappings in this web
+ application is done by using filter-mappingType.
+ The container uses the filter-mapping
+ declarations to decide which filters to apply to a request,
+ and in what order. The container matches the request URI to
+ a Servlet in the normal way. To determine which filters to
+ apply it matches filter-mapping declarations either on
+ servlet-name, or on url-pattern for each filter-mapping
+ element, depending on which style is used. The order in
+ which filters are invoked is the order in which
+ filter-mapping declarations that match a request URI for a
+ servlet appear in the list of filter-mapping elements. The
+ filter-name value must be the value of the filter-name
+ sub-elements of one of the filter declarations in the
+ deployment descriptor.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="filter-name"
- type="j2ee:filter-nameType"/>
+ type="j2ee:filter-nameType"/>
<xsd:choice>
- <xsd:element name="url-pattern"
- type="j2ee:url-patternType"/>
- <xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
+ <xsd:element name="url-pattern"
+ type="j2ee:url-patternType"/>
+ <xsd:element name="servlet-name"
+ type="j2ee:servlet-nameType"/>
</xsd:choice>
<xsd:element name="dispatcher"
- type="j2ee:dispatcherType"
- minOccurs="0" maxOccurs="4"/>
+ type="j2ee:dispatcherType"
+ minOccurs="0" maxOccurs="4"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The logical name of the filter is declare
- by using filter-nameType. This name is used to map the
- filter. Each filter name is unique within the web
- application.
+ The logical name of the filter is declare
+ by using filter-nameType. This name is used to map the
+ filter. Each filter name is unique within the web
+ application.
- Used in: filter, filter-mapping
+ Used in: filter, filter-mapping
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The filterType is used to declare a filter in the web
- application. The filter is mapped to either a servlet or a
- URL pattern in the filter-mapping element, using the
- filter-name value to reference. Filters can access the
- initialization parameters declared in the deployment
- descriptor at runtime via the FilterConfig interface.
+ The filterType is used to declare a filter in the web
+ application. The filter is mapped to either a servlet or a
+ URL pattern in the filter-mapping element, using the
+ filter-name value to reference. Filters can access the
+ initialization parameters declared in the deployment
+ descriptor at runtime via the FilterConfig interface.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="filter-name"
- type="j2ee:filter-nameType"/>
+ type="j2ee:filter-nameType"/>
<xsd:element name="filter-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The fully qualified classname of the filter.
+ The fully qualified classname of the filter.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The init-param element contains a name/value pair as
- an initialization param of a servlet filter
+ The init-param element contains a name/value pair as
+ an initialization param of a servlet filter
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The form-login-configType specifies the login and error
- pages that should be used in form based login. If form based
- authentication is not used, these elements are ignored.
+ The form-login-configType specifies the login and error
+ pages that should be used in form based login. If form based
+ authentication is not used, these elements are ignored.
- Used in: login-config
+ Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="form-login-page"
- type="j2ee:war-pathType">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
- The form-login-page element defines the location in the web
- app where the page that can be used for login can be
- found. The path begins with a leading / and is interpreted
- relative to the root of the WAR.
+ The form-login-page element defines the location in the web
+ app where the page that can be used for login can be
+ found. The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="form-error-page"
- type="j2ee:war-pathType">
- <xsd:annotation>
- <xsd:documentation>
-
- The form-error-page element defines the location in
- the web app where the error page that is displayed
- when login is not successful can be found.
- The path begins with a leading / and is interpreted
- relative to the root of the WAR.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-error-page element defines the location in
+ the web app where the error page that is displayed
+ when login is not successful can be found.
+ The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:documentation>
- The http-method contains an HTTP method recognized by the
- web-app, for example GET, POST, ...
+ The http-method contains an HTTP method recognized by the
+ web-app, for example GET, POST, ...
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="GET"/>
- <xsd:enumeration value="POST"/>
- <xsd:enumeration value="PUT"/>
- <xsd:enumeration value="DELETE"/>
- <xsd:enumeration value="HEAD"/>
- <xsd:enumeration value="OPTIONS"/>
- <xsd:enumeration value="TRACE"/>
+ <xsd:enumeration value="GET"/>
+ <xsd:enumeration value="POST"/>
+ <xsd:enumeration value="PUT"/>
+ <xsd:enumeration value="DELETE"/>
+ <xsd:enumeration value="HEAD"/>
+ <xsd:enumeration value="OPTIONS"/>
+ <xsd:enumeration value="TRACE"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The locale-encoding-mapping-list contains one or more
- locale-encoding-mapping(s).
+ The locale-encoding-mapping-list contains one or more
+ locale-encoding-mapping(s).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="locale-encoding-mapping"
- type="j2ee:locale-encoding-mappingType"
- maxOccurs="unbounded"/>
+ type="j2ee:locale-encoding-mappingType"
+ maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The locale-encoding-mapping contains locale name and
- encoding name. The locale name must be either "Language-code",
- such as "ja", defined by ISO-639 or "Language-code_Country-code",
- such as "ja_JP". "Country code" is defined by ISO-3166.
+ The locale-encoding-mapping contains locale name and
+ encoding name. The locale name must be either "Language-code",
+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
+ such as "ja_JP". "Country code" is defined by ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="locale"
- type="j2ee:localeType"/>
+ type="j2ee:localeType"/>
<xsd:element name="encoding"
- type="j2ee:encodingType"/>
+ type="j2ee:encodingType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The localeType defines valid locale defined by ISO-639-1
- and ISO-3166.
+ The localeType defines valid locale defined by ISO-639-1
+ and ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The login-configType is used to configure the authentication
- method that should be used, the realm name that should be
- used for this application, and the attributes that are
- needed by the form login mechanism.
+ The login-configType is used to configure the authentication
+ method that should be used, the realm name that should be
+ used for this application, and the attributes that are
+ needed by the form login mechanism.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="auth-method"
- type="j2ee:auth-methodType"
- minOccurs="0"/>
+ type="j2ee:auth-methodType"
+ minOccurs="0"/>
<xsd:element name="realm-name"
- type="j2ee:string" minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
- The realm name element specifies the realm name to
- use in HTTP Basic authorization.
+ The realm name element specifies the realm name to
+ use in HTTP Basic authorization.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="form-login-config"
- type="j2ee:form-login-configType"
- minOccurs="0"/>
+ type="j2ee:form-login-configType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The mime-mappingType defines a mapping between an extension
- and a mime type.
+ The mime-mappingType defines a mapping between an extension
+ and a mime type.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
- <xsd:documentation>
+ <xsd:documentation>
- The extension element contains a string describing an
- extension. example: "txt"
+ The extension element contains a string describing an
+ extension. example: "txt"
- </xsd:documentation>
+ </xsd:documentation>
</xsd:annotation>
<xsd:element name="extension"
- type="j2ee:string"/>
+ type="j2ee:string"/>
<xsd:element name="mime-type"
- type="j2ee:mime-typeType"/>
+ type="j2ee:mime-typeType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The mime-typeType is used to indicate a defined mime type.
+ The mime-typeType is used to indicate a defined mime type.
- Example:
- "text/plain"
+ Example:
+ "text/plain"
- Used in: mime-mapping
+ Used in: mime-mapping
</xsd:documentation>
</xsd:annotation>
<xsd:complexType name="nonEmptyStringType">
<xsd:annotation>
<xsd:documentation>
- This type defines a string which contains at least one
- character.
+ This type defines a string which contains at least one
+ character.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:minLength value="1"/>
+ <xsd:minLength value="1"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The security-constraintType is used to associate
- security constraints with one or more web resource
- collections
+ The security-constraintType is used to associate
+ security constraints with one or more web resource
+ collections
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="display-name"
- type="j2ee:display-nameType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="web-resource-collection"
- type="j2ee:web-resource-collectionType"
- maxOccurs="unbounded"/>
+ type="j2ee:web-resource-collectionType"
+ maxOccurs="unbounded"/>
<xsd:element name="auth-constraint"
- type="j2ee:auth-constraintType"
- minOccurs="0"/>
+ type="j2ee:auth-constraintType"
+ minOccurs="0"/>
<xsd:element name="user-data-constraint"
- type="j2ee:user-data-constraintType"
- minOccurs="0"/>
+ type="j2ee:user-data-constraintType"
+ minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The servlet-mappingType defines a mapping between a
- servlet and a url pattern.
+ The servlet-mappingType defines a mapping between a
+ servlet and a url pattern.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
+ type="j2ee:servlet-nameType"/>
<xsd:element name="url-pattern"
- type="j2ee:url-patternType"/>
+ type="j2ee:url-patternType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The servlet-name element contains the canonical name of the
- servlet. Each servlet name is unique within the web
- application.
+ The servlet-name element contains the canonical name of the
+ servlet. Each servlet name is unique within the web
+ application.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
- The servletType is used to declare a servlet.
- It contains the declarative data of a
- servlet. If a jsp-file is specified and the load-on-startup
- element is present, then the JSP should be pre-compiled and
- loaded.
+ The servletType is used to declare a servlet.
+ It contains the declarative data of a
+ servlet. If a jsp-file is specified and the load-on-startup
+ element is present, then the JSP should be pre-compiled and
+ loaded.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="servlet-name"
- type="j2ee:servlet-nameType"/>
+ type="j2ee:servlet-nameType"/>
<xsd:choice>
- <xsd:element name="servlet-class"
- type="j2ee:fully-qualified-classType">
- <xsd:annotation>
- <xsd:documentation>
+ <xsd:element name="servlet-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
- The servlet-class element contains the fully
- qualified class name of the servlet.
+ The servlet-class element contains the fully
+ qualified class name of the servlet.
- </xsd:documentation>
- </xsd:annotation>
- </xsd:element>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
- <xsd:element name="jsp-file"
- type="j2ee:jsp-fileType"/>
+ <xsd:element name="jsp-file"
+ type="j2ee:jsp-fileType"/>
</xsd:choice>
<xsd:element name="init-param"
- type="j2ee:param-valueType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="load-on-startup"
- type="j2ee:xsdIntegerType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The load-on-startup element indicates that this
- servlet should be loaded (instantiated and have
- its init() called) on the start-up of the web
- application. The optional contents of these
- element must be an integer indicating the order in
- which the servlet should be loaded. If the value
- is a negative integer, or the element is not
- present, the container is free to load the servlet
- whenever it chooses. If the value is a positive
- integer or 0, the container must load and
- initialize the servlet as the application is
- deployed. The container must guarantee that
- servlets marked with lower integers are loaded
- before servlets marked with higher integers. The
- container may choose the order of loading of
- servlets with the same load-on-start-up value.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:xsdIntegerType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The load-on-startup element indicates that this
+ servlet should be loaded (instantiated and have
+ its init() called) on the start-up of the web
+ application. The optional contents of these
+ element must be an integer indicating the order in
+ which the servlet should be loaded. If the value
+ is a negative integer, or the element is not
+ present, the container is free to load the servlet
+ whenever it chooses. If the value is a positive
+ integer or 0, the container must load and
+ initialize the servlet as the application is
+ deployed. The container must guarantee that
+ servlets marked with lower integers are loaded
+ before servlets marked with higher integers. The
+ container may choose the order of loading of
+ servlets with the same load-on-start-up value.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="run-as"
- type="j2ee:run-asType"
- minOccurs="0"/>
+ type="j2ee:run-asType"
+ minOccurs="0"/>
<xsd:element name="security-role-ref"
- type="j2ee:security-role-refType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:security-role-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The session-configType defines the session parameters
- for this web application.
+ The session-configType defines the session parameters
+ for this web application.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="session-timeout"
- type="j2ee:xsdIntegerType"
- minOccurs="0">
- <xsd:annotation>
- <xsd:documentation>
-
- The session-timeout element defines the default
- session timeout interval for all sessions created
- in this web application. The specified timeout
- must be expressed in a whole number of minutes.
- If the timeout is 0 or less, the container ensures
- the default behaviour of sessions is never to time
- out. If this element is not specified, the container
- must set its default timeout period.
-
- </xsd:documentation>
- </xsd:annotation>
+ type="j2ee:xsdIntegerType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-timeout element defines the default
+ session timeout interval for all sessions created
+ in this web application. The specified timeout
+ must be expressed in a whole number of minutes.
+ If the timeout is 0 or less, the container ensures
+ the default behaviour of sessions is never to time
+ out. If this element is not specified, the container
+ must set its default timeout period.
+
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
<xsd:annotation>
<xsd:documentation>
- The transport-guaranteeType specifies that the communication
- between client and server should be NONE, INTEGRAL, or
- CONFIDENTIAL. NONE means that the application does not
- require any transport guarantees. A value of INTEGRAL means
- that the application requires that the data sent between the
- client and server be sent in such a way that it can't be
- changed in transit. CONFIDENTIAL means that the application
- requires that the data be transmitted in a fashion that
- prevents other entities from observing the contents of the
- transmission. In most cases, the presence of the INTEGRAL or
- CONFIDENTIAL flag will indicate that the use of SSL is
- required.
-
- Used in: user-data-constraint
+ The transport-guaranteeType specifies that the communication
+ between client and server should be NONE, INTEGRAL, or
+ CONFIDENTIAL. NONE means that the application does not
+ require any transport guarantees. A value of INTEGRAL means
+ that the application requires that the data sent between the
+ client and server be sent in such a way that it can't be
+ changed in transit. CONFIDENTIAL means that the application
+ requires that the data be transmitted in a fashion that
+ prevents other entities from observing the contents of the
+ transmission. In most cases, the presence of the INTEGRAL or
+ CONFIDENTIAL flag will indicate that the use of SSL is
+ required.
+
+ Used in: user-data-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:enumeration value="NONE"/>
- <xsd:enumeration value="INTEGRAL"/>
- <xsd:enumeration value="CONFIDENTIAL"/>
+ <xsd:enumeration value="NONE"/>
+ <xsd:enumeration value="INTEGRAL"/>
+ <xsd:enumeration value="CONFIDENTIAL"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The user-data-constraintType is used to indicate how
- data communicated between the client and container should be
- protected.
+ The user-data-constraintType is used to indicate how
+ data communicated between the client and container should be
+ protected.
- Used in: security-constraint
+ Used in: security-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="transport-guarantee"
- type="j2ee:transport-guaranteeType"/>
+ type="j2ee:transport-guaranteeType"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The elements that use this type designate a path starting
- with a "/" and interpreted relative to the root of a WAR
- file.
+ The elements that use this type designate a path starting
+ with a "/" and interpreted relative to the root of a WAR
+ file.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="j2ee:string">
- <xsd:pattern value="/.*"/>
+ <xsd:pattern value="/.*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- This type contains the recognized versions of
- web-application supported. It is used to designate the
- version of the web application.
+ This type contains the recognized versions of
+ web-application supported. It is used to designate the
+ version of the web application.
</xsd:documentation>
</xsd:annotation>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:group ref="j2ee:descriptionGroup"/>
<xsd:element name="distributable"
- type="j2ee:emptyType"/>
+ type="j2ee:emptyType"/>
<xsd:element name="context-param"
- type="j2ee:param-valueType">
+ type="j2ee:param-valueType">
- <xsd:annotation>
- <xsd:documentation>
+ <xsd:annotation>
+ <xsd:documentation>
- The context-param element contains the declaration
- of a web application's servlet context
- initialization parameters.
+ The context-param element contains the declaration
+ of a web application's servlet context
+ initialization parameters.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="filter"
- type="j2ee:filterType"/>
+ type="j2ee:filterType"/>
<xsd:element name="filter-mapping"
- type="j2ee:filter-mappingType"/>
+ type="j2ee:filter-mappingType"/>
<xsd:element name="listener"
- type="j2ee:listenerType"/>
+ type="j2ee:listenerType"/>
<xsd:element name="servlet"
- type="j2ee:servletType"/>
+ type="j2ee:servletType"/>
<xsd:element name="servlet-mapping"
- type="j2ee:servlet-mappingType"/>
+ type="j2ee:servlet-mappingType"/>
<xsd:element name="session-config"
- type="j2ee:session-configType"/>
+ type="j2ee:session-configType"/>
<xsd:element name="mime-mapping"
- type="j2ee:mime-mappingType"/>
+ type="j2ee:mime-mappingType"/>
<xsd:element name="welcome-file-list"
- type="j2ee:welcome-file-listType"/>
+ type="j2ee:welcome-file-listType"/>
<xsd:element name="error-page"
- type="j2ee:error-pageType"/>
+ type="j2ee:error-pageType"/>
<xsd:element name="jsp-config"
- type="j2ee:jsp-configType"/>
+ type="j2ee:jsp-configType"/>
<xsd:element name="security-constraint"
- type="j2ee:security-constraintType"/>
+ type="j2ee:security-constraintType"/>
<xsd:element name="login-config"
- type="j2ee:login-configType"/>
+ type="j2ee:login-configType"/>
<xsd:element name="security-role"
- type="j2ee:security-roleType"/>
+ type="j2ee:security-roleType"/>
<xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
<xsd:element name="message-destination"
- type="j2ee:message-destinationType"/>
+ type="j2ee:message-destinationType"/>
<xsd:element name="locale-encoding-mapping-list"
- type="j2ee:locale-encoding-mapping-listType"/>
+ type="j2ee:locale-encoding-mapping-listType"/>
</xsd:choice>
<xsd:attribute name="version"
- type="j2ee:web-app-versionType"
- use="required"/>
+ type="j2ee:web-app-versionType"
+ use="required"/>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The web-resource-collectionType is used to identify a subset
- of the resources and HTTP methods on those resources within
- a web application to which a security constraint applies. If
- no HTTP methods are specified, then the security constraint
- applies to all HTTP methods.
+ The web-resource-collectionType is used to identify a subset
+ of the resources and HTTP methods on those resources within
+ a web application to which a security constraint applies. If
+ no HTTP methods are specified, then the security constraint
+ applies to all HTTP methods.
- Used in: security-constraint
+ Used in: security-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="web-resource-name"
- type="j2ee:string">
- <xsd:annotation>
- <xsd:documentation>
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
- The web-resource-name contains the name of this web
- resource collection.
+ The web-resource-name contains the name of this web
+ resource collection.
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
<xsd:element name="description"
- type="j2ee:descriptionType"
- minOccurs="0"
- maxOccurs="unbounded"/>
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
<xsd:element name="url-pattern"
- type="j2ee:url-patternType"
- maxOccurs="unbounded"/>
+ type="j2ee:url-patternType"
+ maxOccurs="unbounded"/>
<xsd:element name="http-method"
- type="j2ee:http-methodType"
- minOccurs="0" maxOccurs="unbounded"/>
+ type="j2ee:http-methodType"
+ minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
- The welcome-file-list contains an ordered list of welcome
- files elements.
+ The welcome-file-list contains an ordered list of welcome
+ files elements.
- Used in: web-app
+ Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="welcome-file"
- type="xsd:string"
- maxOccurs="unbounded">
- <xsd:annotation>
- <xsd:documentation>
+ type="xsd:string"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
- The welcome-file element contains file name to use
- as a default welcome file, such as index.html
+ The welcome-file element contains file name to use
+ as a default welcome file, such as index.html
- </xsd:documentation>
- </xsd:annotation>
+ </xsd:documentation>
+ </xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/>
projects / tomcat7.0 / commitdiff