This is an automated email from the ASF dual-hosted git repository.
markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomcat.git
commit c71527064e58a31ac30de7eb8e1041cdce4a948c
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Fri Jun 5 22:04:51 2020 +0100
Tabs to spaces. Remove trailing whitespace.
---
java/jakarta/servlet/resources/jakartaee_9.xsd | 638 ++++++++++-----------
.../resources/jakartaee_web_services_2_0.xsd | 180 +++---
.../jakartaee_web_services_client_2_0.xsd | 240 ++++----
java/jakarta/servlet/resources/jsp_3_0.xsd | 58 +-
java/jakarta/servlet/resources/web-app_5_0.xsd | 72 +--
java/jakarta/servlet/resources/web-common_5_0.xsd | 218 +++----
6 files changed, 703 insertions(+), 703 deletions(-)
diff --git a/java/jakarta/servlet/resources/jakartaee_9.xsd
b/java/jakarta/servlet/resources/jakartaee_9.xsd
index 16136f9..bd55ed7 100644
--- a/java/jakarta/servlet/resources/jakartaee_9.xsd
+++ b/java/jakarta/servlet/resources/jakartaee_9.xsd
@@ -9,19 +9,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -31,20 +31,20 @@
The following definitions that appear in the common
shareable schema(s) of Jakarta EE deployment descriptors should be
interpreted with respect to the context they are included:
-
+
Deployment Component may indicate one of the following:
Jakarta EE application;
application client;
web application;
enterprise bean;
- resource adapter;
-
+ resource adapter;
+
Deployment File may indicate one of the following:
ear file;
war file;
jar file;
rar file;
-
+
</xsd:documentation>
</xsd:annotation>
@@ -59,10 +59,10 @@
This group keeps the usage of the contained description related
elements consistent across Jakarta EE deployment descriptors.
-
+
All elements may occur multiple times with different languages,
to support localization of the content.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -87,7 +87,7 @@
This group keeps the usage of the contained JNDI environment
reference elements consistent across Jakarta EE deployment descriptors.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -165,7 +165,7 @@
This group collects elements that are common to most
JNDI resource elements.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -177,7 +177,7 @@
<xsd:documentation>
The JNDI name to be looked up to resolve a resource reference.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -191,7 +191,7 @@
This group collects elements that are common to all the
JNDI resource elements. It does not include the lookup-name
element, that is only applicable to some resource elements.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -210,13 +210,13 @@
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>
@@ -235,7 +235,7 @@
<xsd:documentation>
Configuration of an administered object.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -246,7 +246,7 @@
<xsd:documentation>
Description of this administered object.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -257,7 +257,7 @@
The name element specifies the JNDI name of the
administered object being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -268,7 +268,7 @@
<xsd:documentation>
The administered object's interface type.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -278,7 +278,7 @@
<xsd:documentation>
The administered object's class name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -288,7 +288,7 @@
<xsd:documentation>
Resource adapter name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -299,9 +299,9 @@
<xsd:annotation>
<xsd:documentation>
- Property of the administered object property. This may be a
+ Property of the administered object property. This may be a
vendor-specific property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -318,7 +318,7 @@
<xsd:documentation>
Configuration of a Connector Connection Factory resource.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -329,7 +329,7 @@
<xsd:documentation>
Description of this resource.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -340,7 +340,7 @@
The name element specifies the JNDI name of the
resource being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -349,9 +349,9 @@
<xsd:annotation>
<xsd:documentation>
- The fully qualified class name of the connection factory
- interface.
-
+ The fully qualified class name of the connection factory
+ interface.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -361,7 +361,7 @@
<xsd:documentation>
Resource adapter name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -373,7 +373,7 @@
Maximum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -385,7 +385,7 @@
Minimum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -395,9 +395,9 @@
<xsd:annotation>
<xsd:documentation>
- The level of transaction support the connection factory
- needs to support.
-
+ The level of transaction support the connection factory
+ needs to support.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -410,7 +410,7 @@
Resource property. This may be a vendor-specific
property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -427,7 +427,7 @@
<xsd:documentation>
Configuration of a DataSource.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -438,7 +438,7 @@
<xsd:documentation>
Description of this DataSource.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -449,7 +449,7 @@
The name element specifies the JNDI name of the
data source being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -461,7 +461,7 @@
DataSource, XADataSource or ConnectionPoolDataSource
implementation class.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -472,7 +472,7 @@
<xsd:documentation>
Database server name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -483,7 +483,7 @@
<xsd:documentation>
Port number where a server is listening for requests.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -494,7 +494,7 @@
<xsd:documentation>
Name of a database on a server.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -509,7 +509,7 @@
such as <code>serverName</code>, <code>databaseName</code>
and <code>portNumber</code>, the more specific properties will
take precedence and <code>url</code> will be ignored.
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -521,7 +521,7 @@
<xsd:documentation>
User name to use for connection authentication.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -532,7 +532,7 @@
<xsd:documentation>
Password to use for connection authentication.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -545,7 +545,7 @@
JDBC DataSource property. This may be a vendor-specific
property or a less commonly used DataSource property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -557,7 +557,7 @@
Sets the maximum time in seconds that this data source
will wait while attempting to connect to a database.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -569,7 +569,7 @@
Set to false if connections should not participate in
transactions.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -580,7 +580,7 @@
<xsd:documentation>
Isolation level for connections.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -592,7 +592,7 @@
Number of connections that should be created when a
connection pool is initialized.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -604,7 +604,7 @@
Maximum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -616,7 +616,7 @@
Minimum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -629,7 +629,7 @@
The number of seconds that a physical connection should
remain unused in the pool before the connection is
closed for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -641,7 +641,7 @@
The total number of statements that a connection pool
should keep open.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -666,10 +666,10 @@
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).
-
+ description is provided in. The default value is "en" (English).
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -684,8 +684,8 @@
<xsd:documentation>
This type defines a dewey decimal that is used
- to describe versions of documents.
-
+ to describe versions of documents.
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
@@ -703,16 +703,16 @@
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>
-
- 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>
@@ -733,11 +733,11 @@
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an enterprise bean 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 Jakarta EE application unit.
-
+ file in the same Jakarta 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
@@ -746,13 +746,13 @@
Deployment Component that is referencing the enterprise
bean. This allows multiple enterprise beans with the same
ejb-name to be uniquely identified.
-
+
Examples:
-
+
<ejb-link>EmployeeRecord</ejb-link>
-
+
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -772,22 +772,22 @@
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 enterprise bean's reference name used in the code of the
+ - the enterprise bean's 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
+ - 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
+ - optional ejb-link information, used to specify the
referenced enterprise bean
- - optional elements to define injection of the named enterprise
+ - optional elements to define injection of the named enterprise
bean into a component field or property.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -822,17 +822,17 @@
<xsd:annotation>
<xsd:documentation>
<![CDATA[
- The ejb-ref-name element contains the name of an enterprise bean
reference.
- The enterprise bean reference is an entry in the Deployment
Component's
- environment and is relative to the java:comp/env context. The name
must
+ The ejb-ref-name element contains the name of an enterprise bean
reference.
+ The enterprise bean reference is an entry in the Deployment Component's
+ environment and is relative to the java:comp/env context. The name
must
be unique within the Deployment Component.
-
+
It is recommended that name is prefixed with "ejb/".
-
+
Example:
-
+
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -850,25 +850,25 @@
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.
+ to the remote business interface of a 3.0 bean.
The declaration consists of:
-
+
- an optional description
- the enterprise bean's reference name used in the code of
the Deployment Component that's referencing the enterprise
- bean.
+ 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
+ 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 elements to define injection of the named enterprise
bean into a component field or property
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -905,13 +905,13 @@
The ejb-ref-typeType contains the expected type of the
referenced enterprise bean.
-
+
The ejb-ref-type designates a value
that must be one of the following:
-
+
Entity
Session
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -930,8 +930,8 @@
<xsd:documentation>
This type is used to designate an empty
- element when used.
-
+ element when used.
+
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="id"
@@ -950,21 +950,21 @@
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
-
+
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
-
+
If a value is not specified and injection is requested,
no injection will occur and no entry of the specified name
will be created. This allows an initial value to be
specified in the source code without being incorrectly
changed when no override has been specified.
-
+
If a value is not specified and no injection is requested,
- a value must be supplied during deployment.
-
+ a value must be supplied during deployment.
+
This type is used by env-entry elements.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -980,15 +980,15 @@
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
+ 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>
@@ -1005,11 +1005,11 @@
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>
@@ -1026,11 +1026,11 @@
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>
@@ -1051,9 +1051,9 @@
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
-
+
The following are the legal values of env-entry-type-valuesType:
-
+
java.lang.Boolean
java.lang.Byte
java.lang.Character
@@ -1063,15 +1063,15 @@
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:
-
+
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-type>java.lang.Class</env-entry-type>
<env-entry-type>com.example.Color</env-entry-type>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1093,7 +1093,7 @@
of name used in Class.forName(). Tools that need the
canonical name (the name used in source code) will need
to convert this binary name to the canonical name.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1109,9 +1109,9 @@
<xsd:documentation>
This type defines four different values which can designate
- boolean values. This includes values yes and no which are
+ boolean values. This includes values yes and no which are
not designated by xsd:boolean
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1134,12 +1134,12 @@
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.
-
+ GUI tool.
+
The xml:lang attribute defines the language that the
icon file names are provided in. Its value is "en" (English)
- by default.
-
+ by default.
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1153,14 +1153,14 @@
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
-
+
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
-
+
Example:
-
+
<small-icon>employee-service-icon16x16.jpg</small-icon>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1173,17 +1173,17 @@
<![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
+ (32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
-
+
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
-
+
Example:
-
+
<large-icon>employee-service-icon32x32.jpg</large-icon>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1203,22 +1203,22 @@
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
Jakarta EE specifications describe which classes can be an
injection target.
-
+
The injection target name specifies the target within
the specified class. The target is first looked for as a
JavaBeans property name. If not found, the target is
looked for as a field name.
-
+
The specified resource will be injected into the target
during initialization of the class by either calling the
set method for the target property or by setting a value
into the named field.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1233,13 +1233,13 @@
<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
TRANSACTION_SERIALIZABLE
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
@@ -1258,9 +1258,9 @@
<xsd:documentation>
The java-identifierType defines a Java identifier.
- The users of this type should further verify that
+ The users of this type should further verify that
the content does not contain Java reserved keywords.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1280,7 +1280,7 @@
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>
@@ -1300,13 +1300,13 @@
The jdbc-urlType contains the url pattern of the mapping.
It must follow the rules specified in Section 9.3 of the
JDBC Specification where the format is:
-
+
jdbc:<subprotocol>:<subname>
-
+
Example:
-
+
<url>jdbc:mysql://localhost:3307/testdb</url>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1325,7 +1325,7 @@
<xsd:documentation>
Configuration of a Messaging Connection Factory.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1336,7 +1336,7 @@
<xsd:documentation>
Description of this Messaging Connection Factory.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1347,7 +1347,7 @@
The name element specifies the JNDI name of the
messaging connection factory being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1359,10 +1359,10 @@
Fully-qualified name of the messaging connection factory
interface. Permitted values are jakarta.jms.ConnectionFactory,
- jakarta.jms.QueueConnectionFactory, or
+ jakarta.jms.QueueConnectionFactory, or
jakarta.jms.TopicConnectionFactory. If not specified,
jakarta.jms.ConnectionFactory will be used.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1372,10 +1372,10 @@
<xsd:annotation>
<xsd:documentation>
- Fully-qualified name of the messaging connection factory
- implementation class. Ignored if a resource adapter
+ Fully-qualified name of the messaging connection factory
+ implementation class. Ignored if a resource adapter
is used.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1388,7 +1388,7 @@
Resource adapter name. If not specified, the application
server will define the default behavior, which may or may
not involve the use of a resource adapter.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1399,7 +1399,7 @@
<xsd:documentation>
User name to use for connection authentication.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1410,7 +1410,7 @@
<xsd:documentation>
Password to use for connection authentication.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1421,7 +1421,7 @@
<xsd:documentation>
Client id to use for connection.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1434,7 +1434,7 @@
Messaging Connection Factory property. This may be a
vendor-specific
property or a less commonly used ConnectionFactory property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1446,7 +1446,7 @@
Set to false if connections should not participate in
transactions.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1458,7 +1458,7 @@
Maximum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1470,7 +1470,7 @@
Minimum number of connections that should be concurrently
allocated for a connection pool.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1487,7 +1487,7 @@
<xsd:documentation>
Configuration of a Messaging Destination.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1498,7 +1498,7 @@
<xsd:documentation>
Description of this Messaging Destination.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1509,7 +1509,7 @@
The name element specifies the JNDI name of the
messaging destination being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1520,7 +1520,7 @@
Fully-qualified name of the messaging destination interface.
Permitted values are jakarta.jms.Queue and jakarta.jms.Topic
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1534,7 +1534,7 @@
class. Ignored if a resource adapter is used unless the
resource adapter defines more than one destination implementation
class for the specified interface.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1547,7 +1547,7 @@
Resource adapter name. If not specified, the application
server will define the default behavior, which may or may
not involve the use of a resource adapter.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1558,7 +1558,7 @@
<xsd:documentation>
Name of the queue or topic.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1571,7 +1571,7 @@
Messaging Destination property. This may be a vendor-specific
property or a less commonly used Destination property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1591,7 +1591,7 @@
Deployment Component's environment and is relative to the
java:comp/env context. A JNDI name must be unique within the
Deployment Component.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1607,12 +1607,12 @@
<xsd:documentation>
<![CDATA[
The homeType defines the fully-qualified name of
- an enterprise bean's home interface.
-
+ an enterprise bean's home interface.
+
Example:
-
+
<home>com.aardvark.payroll.PayrollHome</home>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1633,12 +1633,12 @@
Note that each class may have only one lifecycle callback
method for any given event and that the method may not
be overloaded.
-
+
If the lifefycle-callback-class element is missing then
the class defining the callback is assumed to be the
component class in scope at the place in the descriptor
in which the callback definition appears.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1659,7 +1659,7 @@
The listenerType indicates the deployment properties for a web
application listener bean.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1673,7 +1673,7 @@
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1691,7 +1691,7 @@
The localType defines the fully-qualified name of an
enterprise bean's local interface.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1708,7 +1708,7 @@
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1724,7 +1724,7 @@
<xsd:documentation>
Configuration of a Mail Session resource.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1735,7 +1735,7 @@
<xsd:documentation>
Description of this Mail Session resource.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1746,7 +1746,7 @@
The name element specifies the JNDI name of the
Mail Session resource being defined.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1757,7 +1757,7 @@
<xsd:documentation>
Storage protocol.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1768,7 +1768,7 @@
<xsd:documentation>
Service provider store protocol implementation class
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1779,7 +1779,7 @@
<xsd:documentation>
Transport protocol.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1790,7 +1790,7 @@
<xsd:documentation>
Service provider transport protocol implementation class
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1801,7 +1801,7 @@
<xsd:documentation>
Mail server host name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1812,7 +1812,7 @@
<xsd:documentation>
Mail server user name.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1823,7 +1823,7 @@
<xsd:documentation>
Password.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1834,7 +1834,7 @@
<xsd:documentation>
Email address to indicate the message sender.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1847,7 +1847,7 @@
Mail server property. This may be a vendor-specific
property.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1865,7 +1865,7 @@
This type is a general type that can be used to declare
parameter/value lists.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1880,7 +1880,7 @@
The param-name element contains the name of a
parameter.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1891,7 +1891,7 @@
The param-value element contains the value of a
parameter.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1909,7 +1909,7 @@
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
@@ -1918,7 +1918,7 @@
the Deployment File's namespace. In general, relative names
are preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1937,7 +1937,7 @@
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,
@@ -1951,14 +1951,14 @@
specified, Synchronized is assumed.
- an optional list of persistence properties
- optional injection targets
-
+
Examples:
-
+
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
</persistence-context-ref>
-
+
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
@@ -1966,7 +1966,7 @@
</persistence-unit-name>
<persistence-context-type>Extended</persistence-context-type>
</persistence-context-ref>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -1985,7 +1985,7 @@
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>
@@ -1998,16 +1998,16 @@
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Jakarta EE application.
-
+
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
- relative to the referencing application component jar file.
+ relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
- persistence unit name may be uniquely identified when the
+ persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2027,11 +2027,11 @@
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
- by a vendor must be ignored. Entries that make use of the
+ by a vendor must be ignored. Entries that make use of the
namespace jakarta.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
jakarta.persistence is reserved for use by the specification.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2048,15 +2048,15 @@
<xsd:annotation>
<xsd:documentation>
- The persistence-context-synchronizationType specifies
+ The persistence-context-synchronizationType specifies
whether a container-managed persistence context is automatically
synchronized with the current transaction.
-
- The value of the persistence-context-synchronization element
+
+ The value of the persistence-context-synchronization element
must be one of the following:
Synchronized
Unsynchronized
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2075,13 +2075,13 @@
<xsd:documentation>
The persistence-context-typeType specifies the transactional
- nature of a persistence context reference.
-
+ nature of a persistence context reference.
+
The value of the persistence-context-type element must be
one of the following:
Transaction
Extended
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2100,7 +2100,7 @@
<xsd:documentation>
Specifies a name/value pair.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -2126,27 +2126,27 @@
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment. It consists of:
-
+
- an optional description
- the persistence unit reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- optional injection targets
-
+
Examples:
-
+
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
</persistence-unit-ref>
-
+
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
</persistence-unit-ref>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2165,7 +2165,7 @@
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>
@@ -2178,16 +2178,16 @@
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Jakarta EE application.
-
+
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
- relative to the referencing application component jar file.
+ relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
- persistence unit name may be uniquely identified when the
+ persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2206,11 +2206,11 @@
<![CDATA[
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
-
+
Example:
-
+
<remote>com.wombat.empl.EmployeeService</remote>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2234,25 +2234,25 @@
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>jakarta.jms.Queue
</resource-env-ref-type>
</resource-env-ref>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2269,10 +2269,10 @@
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
+ 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>
@@ -2286,7 +2286,7 @@
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2312,25 +2312,25 @@
(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>
@@ -2347,9 +2347,9 @@
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.
-
+ java:comp/env context.
+ The name must be unique within a Deployment File.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2363,7 +2363,7 @@
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>
@@ -2392,12 +2392,12 @@
on behalf of the Deployment Component. In the latter case,
the Container uses information that is supplied by the
Deployer.
-
+
The value must be one of the two following:
-
+
Application
Container
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2419,12 +2419,12 @@
obtained through the given resource manager connection
factory reference can be shared. The value, if specified,
must be one of the two following:
-
+
Shareable
Unshareable
-
+
The default value is Shareable.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2443,9 +2443,9 @@
<xsd:documentation>
The run-asType specifies the run-as identity to be
- used for the execution of a component. It contains an
+ 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>
@@ -2468,9 +2468,9 @@
<xsd:documentation>
The role-nameType designates the name of a security role.
-
+
The name must conform to the lexical rules for a token.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2488,9 +2488,9 @@
The security-roleType contains the definition of a security
role. The definition consists of an optional description of
the security role, and the security role name.
-
+
Example:
-
+
<security-role>
<description>
This role includes all employees who are authorized
@@ -2498,7 +2498,7 @@
</description>
<role-name>employee</role-name>
</security-role>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2528,7 +2528,7 @@
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>
@@ -2542,10 +2542,10 @@
<xsd:documentation>
The value of the role-name element must be the String used
- as the parameter to the
+ as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2559,7 +2559,7 @@
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>
@@ -2576,7 +2576,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:QName.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2595,7 +2595,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:boolean.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2614,7 +2614,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:NMTOKEN.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2633,7 +2633,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:anyURI.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2652,7 +2652,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:integer.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2671,7 +2671,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:positiveInteger.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2690,7 +2690,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:nonNegativeInteger.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2709,7 +2709,7 @@
<xsd:documentation>
This type adds an "id" attribute to xsd:string.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2732,7 +2732,7 @@
require trailing/leading space elimination as well as
collapsing the existing whitespace, this base type may be
used.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2752,10 +2752,10 @@
This simple type designates a boolean with only two
permissible values
-
+
- true
- false
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2779,7 +2779,7 @@
If it contains those characters, the container must inform
the developer with a descriptive error message.
The container must preserve all characters including whitespaces.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2797,25 +2797,25 @@
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.
+ among message destination names within the same
+ Deployment File.
- an optional mapped name
- an optional lookup name
-
- Example:
-
+
+ Example:
+
<message-destination>
<message-destination-name>CorporateStocks
</message-destination-name>
</message-destination>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2830,7 +2830,7 @@
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2844,19 +2844,19 @@
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
- component or in one of the other predefined namespaces.
+ component or in one of the other predefined namespaces.
Many application servers provide a way to map these
local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
-
+
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2867,7 +2867,7 @@
<xsd:documentation>
The JNDI name to be looked up to resolve the message destination.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2887,25 +2887,25 @@
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
+ 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>
@@ -2916,7 +2916,7 @@
<message-destination-link>CorporateStocks
</message-destination-link>
</message-destination-ref>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -2934,7 +2934,7 @@
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -2966,13 +2966,13 @@
destination, produced for the destination, or both. The
Assembler makes use of this information in linking producers
of a destination with its consumers.
-
+
The value of the message-destination-usage element must be
one of the following:
Consumes
Produces
ConsumesProduces
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -2994,12 +2994,12 @@
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>jakarta.jms.Queue
</message-destination-type>
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -3018,14 +3018,14 @@
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
-
+
The Assembler sets the value to reflect the flow of messages
between producers and consumers in the application.
-
+
The value must be the message-destination-name of a message
destination in the same Deployment File or in another
Deployment File in the same Jakarta 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
@@ -3034,7 +3034,7 @@
containing Deployment Component that is referencing the
message destination. This allows multiple message
destinations with the same name to be uniquely identified.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -3052,13 +3052,13 @@
The transaction-supportType specifies the level of
transaction support provided by the resource adapter. It is
used by transaction-support elements.
-
+
The value must be one of the following:
-
+
NoTransaction
LocalTransaction
XATransaction
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
diff --git a/java/jakarta/servlet/resources/jakartaee_web_services_2_0.xsd
b/java/jakarta/servlet/resources/jakartaee_web_services_2_0.xsd
index 5bc5315..9f5716b 100644
--- a/java/jakarta/servlet/resources/jakartaee_web_services_2_0.xsd
+++ b/java/jakarta/servlet/resources/jakartaee_web_services_2_0.xsd
@@ -10,19 +10,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -30,7 +30,7 @@
<xsd:documentation>
(C) Copyright International Business Machines Corporation 2002
-
+
</xsd:documentation>
</xsd:annotation>
@@ -43,31 +43,31 @@
Server and the dependencies they have on container resources and
services. The deployment descriptor must be named
"META-INF/webservices.xml" in the web services' jar file.
-
+
Used in: webservices.xml
-
+
All webservices deployment descriptors must indicate the
webservices schema by using the Jakarta EE namespace:
-
+
https://jakarta.ee/xml/ns/jakartaee
-
+
and by indicating the version of the schema by using the version
element as shown below:
-
+
<webservices xmlns="https://jakarta.ee/xml/ns/jakartaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee
- https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_2_0.xsd";
+ https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_2_0.xsd";
version="2.0">
...
</webservices>
-
+
The instance documents may indicate the published version of the
schema using the xsi:schemaLocation attribute for the Jakarta EE
namespace with the following location:
-
+
https://jakarta.ee/xml/ns/jakartaee/jakartaee_web_services_2_0.xsd
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -77,7 +77,7 @@
The following conventions apply to all Jakarta EE
deployment descriptor elements unless indicated otherwise.
-
+
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
@@ -86,7 +86,7 @@
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>
@@ -104,9 +104,9 @@
deployment descriptor. It specifies the set of web service
descriptions that are to be deployed into the Jakarta EE Application
Server
and the dependencies they have on container resources and services.
-
+
Used in: webservices.xml
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:key name="webservice-description-name-key">
@@ -114,9 +114,9 @@
<xsd:documentation>
The webservice-description-name identifies the collection of
- port-components associated with a WSDL file and Jakarta XML RPC
mapping.
+ port-components associated with a WSDL file and Jakarta XML RPC
mapping.
The name must be unique within the deployment descriptor.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:webservice-description"/>
@@ -136,10 +136,10 @@
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 Jakarta XML Web
Services
+
+ This element also associates a WSDL service with a Jakarta XML Web
Services
Provider implementation.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -165,13 +165,13 @@
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>
-
+ <port-component-name>EmployeeService
+ </port-component-name>
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -185,9 +185,9 @@
Defines the name space and local name part of the WSDL
service QName. This is required to be specified for
- port components that are Jakarta XML Web Services
- Provider implementations.
-
+ port components that are Jakarta XML Web Services
+ Provider implementations.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -201,8 +201,8 @@
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 Jakarta XML Web Services Provider
- implementations
-
+ implementations
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -215,9 +215,9 @@
Used to enable or disable SOAP MTOM/XOP mechanism for an
endpoint implementation.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -230,9 +230,9 @@
When MTOM is enabled, binary data above this size in bytes
will be XOP encoded or sent as attachment. Default value is 0.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -243,14 +243,14 @@
<xsd:annotation>
<xsd:documentation>
- This specifies the WS-Addressing requirements for a Jakarta XML
- web service. It corresponds to
jakarta.xml.ws.soap.Addressing
+ This specifies the WS-Addressing requirements for a Jakarta XML
+ web service. It corresponds to
jakarta.xml.ws.soap.Addressing
annotation or its feature jakarta.xml.ws.soap.AddressingFeature.
-
+
See the addressingType for more information.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -263,12 +263,12 @@
Corresponds to the jakarta.xml.ws.RespectBinding annotation
or its corresponding jakarta.xml.ws.RespectBindingFeature web
- service feature. This is used to control whether a Jakarta XML Web
- Services implementation must respect/honor the contents
of the
+ service feature. This is used to control whether a Jakarta XML Web
+ Services implementation must respect/honor the contents of
the
wsdl:binding in the WSDL that is associated with the service.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -282,7 +282,7 @@
Used to specify the protocol binding used by the port-component.
If this element is not specified, then the default binding is
used (SOAP 1.1 over HTTP)
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -296,19 +296,19 @@
The service-endpoint-interface element contains the
fully-qualified name of the port component's Service Endpoint
Interface.
-
+
Used in: port-component
-
+
Example:
- <remote>com.wombat.empl.EmployeeService</remote>
-
+ <remote>com.wombat.empl.EmployeeService</remote>
+
This may not be specified in case there is no Service
Enpoint Interface as is the case with directly using an
implementation class with the @WebService annotation.
-
+
When the port component is a Provider implementation
this is not specified.
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -323,8 +323,8 @@
<xsd:annotation>
<xsd:documentation>
- To be used with Jakarta XML RPC based runtime only.
-
+ To be used with Jakarta XML RPC based runtime only.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -335,8 +335,8 @@
<xsd:annotation>
<xsd:documentation>
- To be used with Jakarta XML Web Services based runtime only.
-
+ To be used with Jakarta XML Web Services based runtime only.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -355,11 +355,11 @@
The service-impl-bean element defines the web service implementation.
A service implementation can be an enterprise bean class or Jakarta
- XML RPC web component. Existing enterprise bean implementations
+ XML RPC web component. Existing enterprise bean implementations
are exposed as a web service using an ejb-link.
-
+
Used in: port-component
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
@@ -382,15 +382,15 @@
The servlet-link element is used in the service-impl-bean element
to specify that a Service Implementation Bean is defined as a
Jakarta XML RPC Service Endpoint.
-
+
The value of the servlet-link element must be the servlet-name of
a Jakarta XML RPC Service Endpoint in the same WAR file.
-
+
Used in: service-impl-bean
-
+
Example:
- <servlet-link>StockQuoteService</servlet-link>
-
+ <servlet-link>StockQuoteService</servlet-link>
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -410,12 +410,12 @@
and the set of Port components associated with the WSDL ports
defined in the WSDL document. There may be multiple
webservice-descriptions defined within a module.
-
+
All WSDL file ports must have a corresponding port-component element
defined.
-
+
Used in: webservices
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -439,7 +439,7 @@
The webservice-description-name identifies the collection of
port-components associated with a WSDL file and Jakarta XML RPC
mapping. The name must be unique within the deployment descriptor.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -452,7 +452,7 @@
The wsdl-file element contains the name of a WSDL file in the
module. The file name is a relative path within the module.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -467,10 +467,10 @@
describes the Jakarta XML 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-Jakarta Enterprise Web Services
based
- runtime is used.
-
+
+ This is not required when JAX-Jakarta Enterprise Web Services based
+ runtime is used.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -484,7 +484,7 @@
Defines the name of the handler. The name must be unique
within the module.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:handler"/>
@@ -510,20 +510,20 @@
<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>
-
-
-
+ 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>
@@ -540,7 +540,7 @@
<xsd:documentation>
The required value for the version is 2.0.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
diff --git
a/java/jakarta/servlet/resources/jakartaee_web_services_client_2_0.xsd
b/java/jakarta/servlet/resources/jakartaee_web_services_client_2_0.xsd
index 72e0435..dd01c6f 100644
--- a/java/jakarta/servlet/resources/jakartaee_web_services_client_2_0.xsd
+++ b/java/jakarta/servlet/resources/jakartaee_web_services_client_2_0.xsd
@@ -10,19 +10,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -30,7 +30,7 @@
<xsd:documentation>
(C) Copyright International Business Machines Corporation 2002
-
+
</xsd:documentation>
</xsd:annotation>
@@ -46,9 +46,9 @@
icons, a declaration of the required Service interface,
an optional WSDL document location, an optional set
of Jakarta XML RPC mappings, an optional QName for the service element,
- an optional set of Service Endpoint Interfaces to be resolved
+ 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>
@@ -59,10 +59,10 @@
<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
+ components in the module use to look up the Web service. It
+ is recommended that all service reference names start with
"service/".
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -72,10 +72,10 @@
<xsd:documentation>
The service-interface element declares the fully qualified class
- name of the Jakarta XML RPC Service interface the client depends
on.
- In most cases the value will be jakarta.xml.rpc.Service. A
Jakarta XML
+ name of the Jakarta XML RPC Service interface the client depends
on.
+ In most cases the value will be jakarta.xml.rpc.Service. A
Jakarta XML
RPC generated Service Interface class may also be specified.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -86,18 +86,18 @@
<xsd:annotation>
<xsd:documentation>
- The service-ref-type element declares the type of the service-ref
+ 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 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 Jakarta XML Web Services runtime where
- the corresponding @WebServiceRef annotation can be used to denote
both
+ 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
+
+ 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>
@@ -110,7 +110,7 @@
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -123,12 +123,12 @@
The jaxrpc-mapping-file element contains the name of a file that
describes the Jakarta XML RPC mapping between the Java interaces
used by
- the application and the WSDL description in the wsdl-file. The
+ 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 Jakarta Enterprise Web Services based
+
+ This is not required when Jakarta Enterprise Web Services based
runtime is used.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -142,7 +142,7 @@
The service-qname element declares the specific WSDL service
element that is being refered to. It is not specified if no
wsdl-file is declared.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -158,7 +158,7 @@
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>
@@ -170,14 +170,14 @@
<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 Jakarta XML RPC based runtime only.
-
+ 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 Jakarta XML RPC based runtime only.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -188,8 +188,8 @@
<xsd:annotation>
<xsd:documentation>
- To be used with Jakarta XML Web Services based runtime only.
-
+ To be used with Jakarta XML Web Services based runtime only.
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -212,7 +212,7 @@
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>
@@ -224,7 +224,7 @@
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -236,10 +236,10 @@
<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 Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -252,9 +252,9 @@
When MTOM is enabled, binary data above this size in bytes
should be XOP encoded or sent as attachment. Default value is 0.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -265,14 +265,14 @@
<xsd:annotation>
<xsd:documentation>
- This specifies the WS-Addressing requirements for a Jakarta XML
+ This specifies the WS-Addressing requirements for a Jakarta XML
web service. It corresponds to jakarta.xml.ws.soap.Addressing
annotation or its feature jakarta.xml.ws.soap.AddressingFeature.
-
+
See the addressingType for more information.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -285,12 +285,12 @@
Corresponds to the jakarta.xml.ws.RespectBinding annotation
or its corresponding jakarta.xml.ws.RespectBindingFeature web
- service feature. This is used to control whether a Jakarta XML Web
+ service feature. This is used to control whether a Jakarta XML Web
Services implementation must respect/honor the contents of the
wsdl:binding in the WSDL that is associated with the service.
-
+
Not to be specified for Jakarta XML RPC runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -304,13 +304,13 @@
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>
@@ -328,7 +328,7 @@
The handler-chains element defines the handlerchains associated with
this
service or service endpoint.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -348,17 +348,17 @@
<xsd:annotation>
<xsd:documentation>
- The handler-chain element defines the handlerchain.
+ The handler-chain element defines the handlerchain.
Handlerchain can be defined such that the handlers in the
handlerchain operate,all ports of a service, on a specific
port or on a list of protocol-bindings. The choice of elements
service-name-pattern, port-name-pattern and protocol-bindings
are used to specify whether the handlers in handler-chain are
- for a service, port or protocol binding. If none of these
+ for a service, port or protocol binding. If none of these
choices are specified with the handler-chain element then the
- handlers specified in the handler-chain will be applied on
+ handlers specified in the handler-chain will be applied on
everything.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -386,9 +386,9 @@
Defines the type used for specifying a list of
protocol-bindingType(s). For e.g.
-
+
##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:list itemType="jakartaee:protocol-bindingType"/>
@@ -401,17 +401,17 @@
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:
-
+ alias the standard binding types:
+
##SOAP11_HTTP
##SOAP11_HTTP_MTOM
##SOAP12_HTTP
##SOAP12_HTTP_MTOM
##XML_HTTP
-
+
Other specifications could define tokens that start with ##
to alias new standard binding URIs that are introduced.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:union memberTypes="xsd:anyURI jakartaee:protocol-URIAliasType"/>
@@ -425,18 +425,18 @@
start with ## which are used to alias existing standard
protocol bindings and support aliases for new standard
binding URIs that are introduced in future specifications.
-
+
The following tokens alias the standard protocol binding
URIs:
-
+
##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http";
- ##SOAP11_HTTP_MTOM =
+ ##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 =
+ ##SOAP12_HTTP_MTOM =
"http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true";
##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http";
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
@@ -451,42 +451,42 @@
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)
-
-
+
+ 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.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
@@ -501,29 +501,29 @@
<xsd:annotation>
<xsd:documentation>
- This specifies the WS-Addressing requirements for a Jakarta XML web
+ This specifies the WS-Addressing requirements for a Jakarta XML web
service. It corresponds to jakarta.xml.ws.soap.Addressing annotation
or its
feature jakarta.xml.ws.soap.AddressingFeature.
-
+
If the "enabled" element is "true", WS-Addressing is enabled.
It means that the endpoint supports WS-Addressing but does not require
its use. The default value for "enabled" is "true".
-
+
If the WS-Addressing is enabled and the "required" element is "true",
it means that the endpoint requires WS-Addressing. The default value
for "required" is "false".
-
+
If WS-Addressing is enabled, the "responses" element determines
if an endpoint requires the use of only anonymous responses,
or only non-anonymous responses, or all. The value of the "responses"
element must be one of the following:
-
+
ANONYMOUS
NON_ANONYMOUS
ALL
-
+
The default value for the "responses" is ALL.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -552,7 +552,7 @@
If WS-Addressing is enabled, this type determines if an endpoint
requires the use of only anonymous responses, or only non-anonymous
responses, or all.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -573,13 +573,13 @@
Corresponds to the jakarta.xml.ws.RespectBinding annotation
or its corresponding jakarta.xml.ws.RespectBindingFeature web
- service feature. This is used to control whether a Jakarta XML
+ service feature. This is used to control whether a Jakarta XML
Web Services implementation must respect/honor the contents of the
wsdl:binding in the WSDL that is associated with the service.
-
+
If the "enabled" element is "true", wsdl:binding in the
associated WSDL, if any, must be respected/honored.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -599,9 +599,9 @@
Declares the handler for a port-component, service-ref. Handlers can
access the init-param name/value pairs using the HandlerInfo interface.
-
+
Used in: port-component, service-ref
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -613,7 +613,7 @@
Defines the name of the handler. The name must be unique within the
module.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -623,7 +623,7 @@
<xsd:documentation>
Defines a fully qualified class name for the handler
implementation.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -635,7 +635,7 @@
<xsd:documentation>
Not to be specified for Jakarta XML Web Services runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -648,9 +648,9 @@
Defines the QName of a SOAP header that will be processed by the
handler.
-
+
Not to be specified for Jakarta XML Web Services runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -663,7 +663,7 @@
The soap-role element contains a SOAP actor definition that the
Handler will play as a role.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -678,9 +678,9 @@
handler should be associated with. If port-name is not
specified, the handler is assumed to be associated with
all ports of the service.
-
+
Not to be specified for Jakarta XML Web Services runtime
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -701,7 +701,7 @@
Defines the name of the handler. The name must be unique
within the module.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:handler"/>
diff --git a/java/jakarta/servlet/resources/jsp_3_0.xsd
b/java/jakarta/servlet/resources/jsp_3_0.xsd
index b374627..4bb8639 100644
--- a/java/jakarta/servlet/resources/jsp_3_0.xsd
+++ b/java/jakarta/servlet/resources/jsp_3_0.xsd
@@ -10,19 +10,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -32,11 +32,11 @@
This is the XML Schema for the JSP 3.0 deployment descriptor
types. The JSP 3.0 schema contains all the special
structures and datatypes that are necessary to use JSP files
- from a web application.
-
- The contents of this schema is used by the web-common_3_1.xsd
- file to define JSP specific content.
-
+ from a web application.
+
+ The contents of this schema is used by the web-common_3_1.xsd
+ file to define JSP specific content.
+
</xsd:documentation>
</xsd:annotation>
@@ -45,7 +45,7 @@
The following conventions apply to all Jakarta EE
deployment descriptor elements unless indicated otherwise.
-
+
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
@@ -54,7 +54,7 @@
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>
@@ -70,7 +70,7 @@
The jsp-configType is used to provide global configuration
information for the JSP files in a web application. It has
two subelements, taglib and jsp-property-group.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -96,7 +96,7 @@
The jsp-file element contains the full path to a JSP file
within the web application beginning with a `/'.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -115,7 +115,7 @@
files so they can be given global property information.
All files so described are deemed to be JSP files. The
following additional properties can be described:
-
+
- Control whether EL is ignored.
- Control whether scripting elements are invalid.
- Indicate pageEncoding information.
@@ -129,7 +129,7 @@
- Indicate the default buffering model for JspWriter
- Control whether error should be raised for the use of
undeclared namespaces in a JSP page.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -148,7 +148,7 @@
EL evaluation is enabled for Web Applications using
a Servlet 2.4 or greater web.xml, and disabled
otherwise.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -169,7 +169,7 @@
in a JSP configuration element matching the document.
It is legal to name the same encoding through
mulitple mechanisms.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -182,7 +182,7 @@
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -198,7 +198,7 @@
If false, the resources are assumed to not
be JSP documents, unless there is another
property group that indicates otherwise.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -215,7 +215,7 @@
the given path will be automatically included (as
in an include directive) at the beginning of each
JSP page in this jsp-property-group.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -232,7 +232,7 @@
the given path will be automatically included (as
in an include directive) at the end of each
JSP page in this jsp-property-group.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -247,7 +247,7 @@
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -261,7 +261,7 @@
must be removed from the response output. It has no
effect on JSP documents (XML syntax). Disabled (false)
by default.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -275,7 +275,7 @@
contentType page directive. It specifies the default
response contentType if the page directive does not include
a contentType attribute.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -289,7 +289,7 @@
buffer page directive. It specifies if buffering should be
used for the output to response, and if so, the size of the
buffer to use.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -304,7 +304,7 @@
set to true, then an error must be raised during the translation
time when an undeclared tag is used in a JSP page. Disabled
(false) by default.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -325,7 +325,7 @@
available to the application. This can be done
to override implicit map entries from TLD files and
from the container.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -340,7 +340,7 @@
absolute URI specification, or a relative URI.
There should be no entries in web.xml with the
same taglib-uri value.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -353,7 +353,7 @@
(as a resource relative to the root of the web
application) where to find the Tag Library
Description file for the tag library.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
diff --git a/java/jakarta/servlet/resources/web-app_5_0.xsd
b/java/jakarta/servlet/resources/web-app_5_0.xsd
index c7fcb4b..017e512 100644
--- a/java/jakarta/servlet/resources/web-app_5_0.xsd
+++ b/java/jakarta/servlet/resources/web-app_5_0.xsd
@@ -10,19 +10,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -34,25 +34,25 @@
web application's war file. All Servlet deployment descriptors
must indicate the web application schema by using the Jakarta EE
namespace:
-
+
https://jakarta.ee/xml/ns/jakartaee
-
+
and by indicating the version of the schema by
using the version element as shown below:
-
+
<web-app xmlns="https://jakarta.ee/xml/ns/jakartaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="..."
version="5.0">
...
</web-app>
-
+
The instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for Jakarta EE
namespace with the following location:
-
+
https://jakarta.ee/xml/ns/jakartaee/web-app_5_0.xsd
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -62,7 +62,7 @@
The following conventions apply to all Jakarta EE
deployment descriptor elements unless indicated otherwise.
-
+
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
@@ -71,7 +71,7 @@
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>
@@ -99,7 +99,7 @@
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="web-common-servlet-name-uniqueness">
@@ -108,7 +108,7 @@
The servlet element contains the name of a servlet.
The name must be unique within the web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:servlet"/>
@@ -120,7 +120,7 @@
The filter element contains the name of a filter.
The name must be unique within the web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:filter"/>
@@ -130,15 +130,15 @@
<xsd:annotation>
<xsd:documentation>
- The ejb-local-ref-name element contains the name of an
- enterprise bean reference. The enterprise
+ The ejb-local-ref-name element contains the name of an
+ enterprise bean reference. The enterprise
bean reference is an entry in the web
application's environment and is relative to the
java:comp/env context. The name must be unique within
the web application.
-
+
It is recommended that name is prefixed with "ejb/".
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:ejb-local-ref"/>
@@ -148,14 +148,14 @@
<xsd:annotation>
<xsd:documentation>
- The ejb-ref-name element contains the name of an
- enterprise bean reference. The enterprise bean
- reference is an entry in the web application's environment
- and is relative to the java:comp/env context.
+ The ejb-ref-name element contains the name of an
+ enterprise bean reference. The enterprise bean
+ reference is an entry in the web application's environment
+ and is relative to the java:comp/env context.
The name must be unique within the web application.
-
+
It is recommended that name is prefixed with "ejb/".
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:ejb-ref"/>
@@ -170,7 +170,7 @@
environment entry name used in the web application code.
The name is a JNDI name relative to the java:comp/env
context and must be unique within a web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:resource-env-ref"/>
@@ -185,7 +185,7 @@
environment entry name used in the web application code.
The name is a JNDI name relative to the java:comp/env
context and must be unique within a web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:message-destination-ref"/>
@@ -199,7 +199,7 @@
resource manager connection factory reference. The name
is a JNDI name relative to the java:comp/env context.
The name must be unique within a web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:resource-ref"/>
@@ -213,7 +213,7 @@
application's environment entry. The name is a JNDI
name relative to the java:comp/env context. The name
must be unique within a web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:env-entry"/>
@@ -225,7 +225,7 @@
A role-name-key is specified to allow the references
from the security-role-refs.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:security-role"/>
@@ -238,7 +238,7 @@
The keyref indicates the references from
security-role-ref to a specified role-name.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="jakartaee:servlet/jakartaee:security-role-ref"/>
@@ -269,7 +269,7 @@
Servlet containers may provide vendor specific configuration
options that allows specifying a value that overrides the value
specified here.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -280,7 +280,7 @@
When specified, this element provides a default request
character encoding of the web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -291,7 +291,7 @@
When specified, this element provides a default response
character encoding of the web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -305,7 +305,7 @@
security-constrant, this element causes all HTTP methods that
are NOT covered (by a security constraint) at the url-pattern
to be denied.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -323,7 +323,7 @@
<xsd:documentation>
Please see section 8.2.2 of the specification for details.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:choice minOccurs="0"
diff --git a/java/jakarta/servlet/resources/web-common_5_0.xsd
b/java/jakarta/servlet/resources/web-common_5_0.xsd
index ee12bea..bf8132d 100644
--- a/java/jakarta/servlet/resources/web-common_5_0.xsd
+++ b/java/jakarta/servlet/resources/web-common_5_0.xsd
@@ -10,19 +10,19 @@
<xsd:documentation>
Copyright (c) 2009, 2020 Oracle and/or its affiliates. All rights
reserved.
-
+
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
-
+
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
-
+
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-
+
</xsd:documentation>
</xsd:annotation>
@@ -34,25 +34,25 @@
web application's war file. All Servlet deployment descriptors
must indicate the web common schema by using the Jakarta EE
namespace:
-
+
https://jakarta.ee/xml/ns/jakartaee
-
+
and by indicating the version of the schema by
using the version element as shown below:
-
+
<web-app xmlns="https://jakarta.ee/xml/ns/jakartaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="..."
version="5.0">
...
</web-app>
-
+
The instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for Jakarta EE
namespace with the following location:
-
+
https://jakarta.ee/xml/ns/jakartaee/web-common_5_0.xsd
-
+
]]>
</xsd:documentation>
</xsd:annotation>
@@ -62,7 +62,7 @@
The following conventions apply to all Jakarta EE
deployment descriptor elements unless indicated otherwise.
-
+
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
@@ -71,7 +71,7 @@
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>
@@ -92,7 +92,7 @@
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -148,17 +148,17 @@
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
-
+
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
-
+
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
@@ -183,7 +183,7 @@
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>
@@ -214,9 +214,9 @@
using the configured mechanism. Legal values are "BASIC",
"DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
authentication scheme.
-
+
Used in: login-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -233,7 +233,7 @@
The dispatcher has five legal values: FORWARD, REQUEST,
INCLUDE, ASYNC, and ERROR.
-
+
A value of FORWARD means the Filter will be applied under
RequestDispatcher.forward() calls.
A value of REQUEST means the Filter will be applied under
@@ -244,11 +244,11 @@
calls dispatched from an AsyncContext.
A value of ERROR means the Filter will be applied under the
error page mechanism.
-
+
The absence of any dispatcher elements in a filter-mapping
indicates a default of applying filters only under ordinary
client calls to the path or servlet.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -270,9 +270,9 @@
<xsd:documentation>
The error-code contains an HTTP error code, ex: 404
-
+
Used in: error-page
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -294,19 +294,19 @@
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
-
+
Error-page declarations using the exception-type element in
the deployment descriptor must be unique up to the class name of
the exception-type. Similarly, error-page declarations using the
error-code element must be unique in the deployment descriptor
up to the status code.
-
+
If an error-page element in the deployment descriptor does not
contain an exception-type or an error-code element, the error
page is a default error page.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -321,7 +321,7 @@
The exception-type contains a fully qualified class
name of a Java exception type.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -335,7 +335,7 @@
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -357,9 +357,9 @@
filter-name value to reference. Filters can access the
initialization parameters declared in the deployment
descriptor at runtime via the FilterConfig interface.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -374,7 +374,7 @@
<xsd:documentation>
The fully qualified classname of the filter.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -390,7 +390,7 @@
The init-param element contains a name/value pair as
an initialization param of a servlet filter
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -421,7 +421,7 @@
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>
@@ -452,7 +452,7 @@
This type defines a string which contains at least one
character.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -473,9 +473,9 @@
by using filter-nameType. This name is used to map the
filter. Each filter name is unique within the web
application.
-
+
Used in: filter, filter-mapping
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -493,9 +493,9 @@
The form-login-configType specifies the login and error
pages that should be used in form based login. If form based
authentication is not used, these elements are ignored.
-
+
Used in: login-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -508,7 +508,7 @@
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -522,7 +522,7 @@
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>
@@ -536,7 +536,7 @@
<xsd:documentation>
A HTTP method type as defined in HTTP 1.1 section 2.2.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
@@ -565,9 +565,9 @@
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -582,7 +582,7 @@
The realm name element specifies the realm name to
use in HTTP Basic authorization.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -603,9 +603,9 @@
The mime-mappingType defines a mapping between an extension
and a mime type.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -614,7 +614,7 @@
The extension element contains a string describing an
extension. example: "txt"
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:element name="extension"
@@ -634,12 +634,12 @@
<xsd:documentation>
The mime-typeType is used to indicate a defined mime type.
-
+
Example:
"text/plain"
-
+
Used in: mime-mapping
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -659,9 +659,9 @@
The security-constraintType is used to associate
security constraints with one or more web resource
collections
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -695,9 +695,9 @@
servlet. If a jsp-file is specified and the load-on-startup
element is present, then the JSP should be precompiled and
loaded.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -713,7 +713,7 @@
The servlet-class element contains the fully
qualified class name of the servlet.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -746,7 +746,7 @@
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>
@@ -781,9 +781,9 @@
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -808,7 +808,7 @@
The servlet-name element contains the canonical name of the
servlet. Each servlet name is unique within the web
application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -825,9 +825,9 @@
The session-configType defines the session parameters
for this web application.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -845,7 +845,7 @@
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>
@@ -857,7 +857,7 @@
The cookie-config element defines the configuration of the
session tracking cookies created by this web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -870,7 +870,7 @@
The tracking-mode element defines the tracking modes
for sessions created by this web application
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -888,9 +888,9 @@
The cookie-configType defines the configuration for the
session tracking cookies of this web application.
-
+
Used in: session-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -903,7 +903,7 @@
The name that will be assigned to any session tracking
cookies created by this web application.
The default is JSESSIONID
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -915,7 +915,7 @@
The domain name that will be assigned to any session tracking
cookies created by this web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -927,7 +927,7 @@
The path that will be assigned to any session tracking
cookies created by this web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -939,7 +939,7 @@
The comment that will be assigned to any session tracking
cookies created by this web application.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -951,7 +951,7 @@
Specifies whether any session tracking cookies created
by this web application will be marked as HttpOnly
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -968,7 +968,7 @@
initiated the corresponding session.
When false, the session cookie should only be marked secure
if the request that initiated the session was secure.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -981,7 +981,7 @@
The lifetime (in seconds) that will be assigned to any
session tracking cookies created by this web application.
Default is -1
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1000,9 +1000,9 @@
The name that will be assigned to any session tracking
cookies created by this web application.
The default is JSESSIONID
-
+
Used in: cookie-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1019,9 +1019,9 @@
The domain name that will be assigned to any session tracking
cookies created by this web application.
-
+
Used in: cookie-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1038,9 +1038,9 @@
The path that will be assigned to any session tracking
cookies created by this web application.
-
+
Used in: cookie-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1057,9 +1057,9 @@
The comment that will be assigned to any session tracking
cookies created by this web application.
-
+
Used in: cookie-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1076,9 +1076,9 @@
The tracking modes for sessions created by this web
application
-
+
Used in: session-config
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
@@ -1109,9 +1109,9 @@
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>
@@ -1133,9 +1133,9 @@
The user-data-constraintType is used to indicate how
data communicated between the client and container should be
protected.
-
+
Used in: security-constraint
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1160,7 +1160,7 @@
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>
@@ -1177,7 +1177,7 @@
This type contains the recognized versions of
web-application supported. It is used to designate the
version of the web application.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
@@ -1201,9 +1201,9 @@
except those identified in the collection.
http-method-omission and http-method elements are never
mixed in the same collection.
-
+
Used in: security-constraint
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1214,7 +1214,7 @@
The web-resource-name contains the name of this web
resource collection.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1236,7 +1236,7 @@
Each http-method names an HTTP method to which the
constraint applies.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1249,7 +1249,7 @@
Each http-method-omission names an HTTP method to
which the constraint does not apply.
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1268,9 +1268,9 @@
The welcome-file-list contains an ordered list of welcome
files elements.
-
+
Used in: web-app
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1282,7 +1282,7 @@
The welcome-file element contains file name to use
as a default welcome file, such as index.html
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1297,7 +1297,7 @@
The localeType defines valid locale defined by ISO-639-1
and ISO-3166.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
@@ -1310,7 +1310,7 @@
<xsd:documentation>
The encodingType defines IANA character sets.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
@@ -1327,7 +1327,7 @@
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1350,7 +1350,7 @@
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>
@@ -1375,7 +1375,7 @@
of this application resource relative to other application
configuration resources.
See section 8.2.2 of the specification for details.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="id"
@@ -1391,7 +1391,7 @@
This element specifies configuration information related to the
handling of multipart/form-data requests.
-
+
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
@@ -1403,7 +1403,7 @@
<xsd:documentation>
The directory location where uploaded files will be stored
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1415,7 +1415,7 @@
<xsd:documentation>
The maximum size limit of uploaded files
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1427,7 +1427,7 @@
<xsd:documentation>
The maximum size limit of multipart/form-data requests
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
@@ -1440,7 +1440,7 @@
The size threshold after which an uploaded file will be
written to disk
-
+
</xsd:documentation>
</xsd:annotation>
</xsd:element>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
