XML Schema Documentation
Jun 24, 2008 1:57:07 PM
Namespace Summary
| Schema Summary |
| javaee_5.xsd |
@(#)javaee_5.xsds 1.65 06/02/17
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Imports Schema: -
Includes Schema: -
Included in Schemas (2): -
|
| javaee_web_services_client_1_2.xsd |
@(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Included in Schema: -
|
| jsp_2_1.xsd |
@(#)jsp_2_1.xsds 1.5 08/11/05
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Includes Schema: -
Included in Schema: -
|
| web-app_2_5.xsd |
@(#)web-app_2_5.xsds 1.68 07/03/09
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Includes Schemas (2): -
|
| xml.xsd |
See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace. Target Namespace: -
Components: -
Schema Location: -
Imported by Schema: -
|
Namespace "http://java.sun.com/xml/ns/javaee"
Targeting Schemas (4):
-
Components:
-
| Schema Summary |
| javaee_5.xsd |
@(#)javaee_5.xsds 1.65 06/02/17
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Imports Schema: -
Includes Schema: -
Included in Schemas (2): -
|
| javaee_web_services_client_1_2.xsd |
@(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Included in Schema: -
|
| jsp_2_1.xsd |
@(#)jsp_2_1.xsds 1.5 08/11/05
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Includes Schema: -
Included in Schema: -
|
| web-app_2_5.xsd |
@(#)web-app_2_5.xsds 1.68 07/03/09
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. Target Namespace: -
Components: -
Schema Location: -
Includes Schemas (2): -
|
| Complex Type Summary |
| javaee:auth-constraintType |
The auth-constraintType indicates the user roles that
should be permitted access to this resource
collection.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:auth-methodType |
The auth-methodType is used to configure the authentication
mechanism for the web application.
|
| javaee:descriptionType |
The description type is used by a description element to
provide text describing the parent element.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:dispatcherType |
The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
and ERROR.
|
| javaee:display-nameType |
The display-name type contains a short name that is intended
to be displayed by tools.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:ejb-linkType |
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an EJB reference is linked to enterprise bean.
|
| javaee:ejb-local-refType |
The ejb-local-refType is used by ejb-local-ref elements for
the declaration of a reference to an enterprise bean's local
home or to the local business interface of a 3.0 bean.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:ejb-ref-nameType |
The ejb-ref-name element contains the name of an EJB
reference.
|
| javaee:ejb-ref-typeType |
The ejb-ref-typeType contains the expected type of the
referenced enterprise bean.
|
| javaee:ejb-refType |
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.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:emptyType |
This type is used to designate an empty
element when used.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:env-entry-type-valuesType |
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
|
| javaee:env-entryType |
The env-entryType is used to declare an application's
environment entry.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:error-codeType |
The error-code contains an HTTP error code, ex: 404
Used in: error-page
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:error-pageType |
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:filter-mappingType |
Declaration of the filter mappings in this web
application is done by using filter-mappingType.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:filter-nameType |
The logical name of the filter is declare
by using filter-nameType.
|
| javaee:filterType |
The filterType is used to declare a filter in the web
application.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:form-login-configType |
The form-login-configType specifies the login and error
pages that should be used in form based login.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:fully-qualified-classType |
The elements that use this type designate the name of a
Java class or interface.
|
| javaee:generic-booleanType |
This type defines four different values which can designate
boolean values.
Content: |
|
Defined: |
|
Used: |
never |
|
| javaee:homeType |
The homeType defines the fully-qualified name of
an enterprise bean's home interface.
|
| javaee:iconType |
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.
Content: |
|
Defined: |
|
Includes: |
definitions of 2 attributes and 2 elements |
Used: |
|
|
| javaee:injection-targetType |
An injection target specifies a class and a name within
that class into which a resource should be injected.
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
| javaee:java-identifierType |
The java-identifierType defines a Java identifier.
|
| javaee:java-typeType |
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.
Content: |
|
Defined: |
|
Used: |
never |
|
| javaee:jndi-nameType |
The jndi-nameType type designates a JNDI name in the
Deployment Component's environment and is relative to the
java:comp/env context.
|
| javaee:jsp-configType |
The jsp-configType is used to provide global configuration
information for the JSP files in a web application.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:jsp-fileType |
The jsp-file element contains the full path to a JSP file
within the web application beginning with a `/'.
|
| javaee:jsp-property-groupType |
The jsp-property-groupType is used to group a number of
files so they can be given global property information.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
|
| javaee:lifecycle-callbackType |
The lifecycle-callback type specifies a method on a
class to be called when a lifecycle event occurs.
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
| javaee:listenerType |
The listenerType indicates the deployment properties for a web
application listener bean.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:local-homeType |
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
|
| javaee:locale-encoding-mapping-listType |
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:locale-encoding-mappingType |
The locale-encoding-mapping contains locale name and
encoding name.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:localType |
The localType defines the fully-qualified name of an
enterprise bean's local interface.
|
| javaee:login-configType |
The login-configType is used to configure the authentication
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:message-destination-linkType |
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
|
| javaee:message-destination-refType |
The message-destination-ref element contains a declaration
of Deployment Component's reference to a message destination
associated with a resource in Deployment Component's
environment.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:message-destination-typeType |
The message-destination-typeType specifies the type of
the destination.
|
| javaee:message-destination-usageType |
The message-destination-usageType specifies the use of the
message destination indicated by the reference.
|
| javaee:message-destinationType |
The message-destinationType specifies a message
destination.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:mime-mappingType |
The mime-mappingType defines a mapping between an extension
and a mime type.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:mime-typeType |
The mime-typeType is used to indicate a defined mime type.
|
| javaee:nonEmptyStringType |
This type defines a string which contains at least one
character.
|
| javaee:param-valueType |
This type is a general type that can be used to declare
parameter/value lists.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:pathType |
The elements that use this type designate either a relative
path or an absolute path starting with a "/".
|
| javaee:persistence-context-refType |
The persistence-context-ref element contains a declaration
of Deployment Component's reference to a persistence context
associated within a Deployment Component's
environment.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:persistence-context-typeType |
The persistence-context-typeType specifies the transactional
nature of a persistence context reference.
|
| javaee:persistence-unit-refType |
The persistence-unit-ref element contains a declaration
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:port-component-refType |
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:propertyType |
Specifies a name/value pair.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:remoteType |
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
|
| javaee:res-authType |
The res-authType specifies whether the Deployment Component
code signs on programmatically to the resource manager, or
whether the Container will sign on to the resource manager
on behalf of the Deployment Component.
|
| javaee:res-sharing-scopeType |
The res-sharing-scope type specifies whether connections
obtained through the given resource manager connection
factory reference can be shared.
|
| javaee:resource-env-refType |
The resource-env-refType is used to define
resource-env-type elements.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:resource-refType |
The resource-refType contains a declaration of a
Deployment Component's reference to an external resource.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:role-nameType |
The role-nameType designates the name of a security role.
|
| javaee:run-asType |
The run-asType specifies the run-as identity to be
used for the execution of a component.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:security-constraintType |
The security-constraintType is used to associate
security constraints with one or more web resource
collections
Used in: web-app
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:security-role-refType |
The security-role-refType contains the declaration of a
security role reference in a component's or a
Deployment Component's code.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:security-roleType |
The security-roleType contains the definition of a security
role.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:service-ref_handler-chainsType |
The handler-chains element defines the handlerchains associated with this
service or service endpoint.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:service-ref_handler-chainType |
The handler-chain element defines the handlerchain.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:service-ref_handlerType |
Declares the handler for a port-component.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:service-refType |
The service-ref element declares a reference to a Web
service.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
|
| javaee:servlet-mappingType |
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:servlet-nameType |
The servlet-name element contains the canonical name of the
servlet.
|
| javaee:servletType |
The servletType is used to declare a servlet.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 7 elements |
Used: |
|
|
| javaee:session-configType |
The session-configType defines the session parameters
for this web application.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:string |
This is a special string datatype that is defined by Java EE as
a base type for defining collapsed strings.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:taglibType |
The taglibType defines the syntax for declaring in
the deployment descriptor that a tag library is
available to the application.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:transport-guaranteeType |
The transport-guaranteeType specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL.
|
| javaee:true-falseType |
This simple type designates a boolean with only two
permissible values
- true
- false
|
| javaee:url-patternType |
The url-patternType contains the url pattern of the mapping.
Content: |
simple |
Defined: |
|
Used: |
|
|
| javaee:user-data-constraintType |
The user-data-constraintType is used to indicate how
data communicated between the client and container should be
protected.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:war-pathType |
The elements that use this type designate a path starting
with a "/" and interpreted relative to the root of a WAR
file.
|
| javaee:web-appType |
Content: |
|
Defined: |
|
Includes: |
definitions of 3 attributes and 17 elements |
Used: |
|
|
| javaee:web-resource-collectionType |
The web-resource-collectionType is used to identify a subset
of the resources and HTTP methods on those resources within
a web application to which a security constraint applies.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:welcome-file-listType |
The welcome-file-list contains an ordered list of welcome
files elements.
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:xsdAnyURIType |
This type adds an "id" attribute to xsd:anyURI.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdBooleanType |
This type adds an "id" attribute to xsd:boolean.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdIntegerType |
This type adds an "id" attribute to xsd:integer.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdNMTOKENType |
This type adds an "id" attribute to xsd:NMTOKEN.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
|
| javaee:xsdNonNegativeIntegerType |
This type adds an "id" attribute to xsd:nonNegativeInteger.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
|
| javaee:xsdPositiveIntegerType |
This type adds an "id" attribute to xsd:positiveInteger.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdQNameType |
This type adds an "id" attribute to xsd:QName.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdStringType |
This type adds an "id" attribute to xsd:string.
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| Element Group Summary |
| javaee:descriptionGroup |
This group keeps the usage of the contained description related
elements consistent across Java EE deployment descriptors.
Content: |
|
Defined: |
|
Includes: |
definitions of 3 elements |
Used: |
|
|
| javaee:jndiEnvironmentRefsGroup |
This group keeps the usage of the contained JNDI environment
reference elements consistent across Java EE deployment descriptors.
Content: |
|
Defined: |
|
Includes: |
definitions of 10 elements |
Used: |
|
|
| javaee:resourceGroup |
This group collects elements that are common to all the
JNDI resource elements.
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
| javaee:service-refGroup |
Content: |
|
Defined: |
|
Includes: |
definition of 1 element |
Used: |
|
|
XML Schema "javaee_5.xsd"
Target Namespace:
-
Components:
-
Schema Location:
-
Imports Schema:
-
Includes Schema:
-
Included in Schemas (2):
-
Annotation
Annotation 1:
@(#)javaee_5.xsds 1.65 06/02/17
Annotation 2:
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
Annotation 3:
The following definitions that appear in the common
shareable schema(s) of J2EE deployment descriptors should be
interpreted with respect to the context they are included:
Deployment Component may indicate one of the following:
j2ee application;
application client;
web application;
enterprise bean;
resource adapter;
Deployment File may indicate one of the following:
ear file;
war file;
jar file;
rar file;
| Complex Type Summary |
| javaee:descriptionType |
The description type is used by a description element to
provide text describing the parent element.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:display-nameType |
The display-name type contains a short name that is intended
to be displayed by tools.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:ejb-linkType |
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an EJB reference is linked to enterprise bean.
|
| javaee:ejb-local-refType |
The ejb-local-refType is used by ejb-local-ref elements for
the declaration of a reference to an enterprise bean's local
home or to the local business interface of a 3.0 bean.
Content: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:ejb-ref-nameType |
The ejb-ref-name element contains the name of an EJB
reference.
|
| javaee:ejb-ref-typeType |
The ejb-ref-typeType contains the expected type of the
referenced enterprise bean.
|
| javaee:ejb-refType |
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.
Content: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:emptyType |
This type is used to designate an empty
element when used.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:env-entry-type-valuesType |
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
|
| javaee:env-entryType |
The env-entryType is used to declare an application's
environment entry.
Content: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:fully-qualified-classType |
The elements that use this type designate the name of a
Java class or interface.
|
| javaee:generic-booleanType |
This type defines four different values which can designate
boolean values.
|
| javaee:homeType |
The homeType defines the fully-qualified name of
an enterprise bean's home interface.
|
| javaee:iconType |
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.
Content: |
|
Includes: |
definitions of 2 attributes and 2 elements |
Used: |
|
|
| javaee:injection-targetType |
An injection target specifies a class and a name within
that class into which a resource should be injected.
Content: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
| javaee:java-identifierType |
The java-identifierType defines a Java identifier.
|
| javaee:java-typeType |
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.
|
| javaee:jndi-nameType |
The jndi-nameType type designates a JNDI name in the
Deployment Component's environment and is relative to the
java:comp/env context.
|
| javaee:lifecycle-callbackType |
The lifecycle-callback type specifies a method on a
class to be called when a lifecycle event occurs.
Content: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
| javaee:listenerType |
The listenerType indicates the deployment properties for a web
application listener bean.
Content: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:local-homeType |
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
|
| javaee:localType |
The localType defines the fully-qualified name of an
enterprise bean's local interface.
|
| javaee:message-destination-linkType |
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
|
| javaee:message-destination-refType |
The message-destination-ref element contains a declaration
of Deployment Component's reference to a message destination
associated with a resource in Deployment Component's
environment.
Content: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:message-destination-typeType |
The message-destination-typeType specifies the type of
the destination.
|
| javaee:message-destination-usageType |
The message-destination-usageType specifies the use of the
message destination indicated by the reference.
|
| javaee:message-destinationType |
The message-destinationType specifies a message
destination.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:param-valueType |
This type is a general type that can be used to declare
parameter/value lists.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:pathType |
The elements that use this type designate either a relative
path or an absolute path starting with a "/".
|
| javaee:persistence-context-refType |
The persistence-context-ref element contains a declaration
of Deployment Component's reference to a persistence context
associated within a Deployment Component's
environment.
Content: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:persistence-context-typeType |
The persistence-context-typeType specifies the transactional
nature of a persistence context reference.
|
| javaee:persistence-unit-refType |
The persistence-unit-ref element contains a declaration
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:propertyType |
Specifies a name/value pair.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:remoteType |
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
|
| javaee:res-authType |
The res-authType specifies whether the Deployment Component
code signs on programmatically to the resource manager, or
whether the Container will sign on to the resource manager
on behalf of the Deployment Component.
|
| javaee:res-sharing-scopeType |
The res-sharing-scope type specifies whether connections
obtained through the given resource manager connection
factory reference can be shared.
|
| javaee:resource-env-refType |
The resource-env-refType is used to define
resource-env-type elements.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:resource-refType |
The resource-refType contains a declaration of a
Deployment Component's reference to an external resource.
Content: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
|
| javaee:role-nameType |
The role-nameType designates the name of a security role.
|
| javaee:run-asType |
The run-asType specifies the run-as identity to be
used for the execution of a component.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:security-role-refType |
The security-role-refType contains the declaration of a
security role reference in a component's or a
Deployment Component's code.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:security-roleType |
The security-roleType contains the definition of a security
role.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:string |
This is a special string datatype that is defined by Java EE as
a base type for defining collapsed strings.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:true-falseType |
This simple type designates a boolean with only two
permissible values
- true
- false
|
| javaee:url-patternType |
The url-patternType contains the url pattern of the mapping.
|
| javaee:xsdAnyURIType |
This type adds an "id" attribute to xsd:anyURI.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdBooleanType |
This type adds an "id" attribute to xsd:boolean.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdIntegerType |
This type adds an "id" attribute to xsd:integer.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdNMTOKENType |
This type adds an "id" attribute to xsd:NMTOKEN.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
|
| javaee:xsdNonNegativeIntegerType |
This type adds an "id" attribute to xsd:nonNegativeInteger.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
|
| javaee:xsdPositiveIntegerType |
This type adds an "id" attribute to xsd:positiveInteger.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdQNameType |
This type adds an "id" attribute to xsd:QName.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:xsdStringType |
This type adds an "id" attribute to xsd:string.
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| Simple Type Summary |
| javaee:dewey-versionType |
This type defines a dewey decimal that is used
to describe versions of documents.
|
| Element Group Summary |
| javaee:descriptionGroup |
This group keeps the usage of the contained description related
elements consistent across Java EE deployment descriptors.
Content: |
|
Includes: |
definitions of 3 elements |
Used: |
|
|
| javaee:jndiEnvironmentRefsGroup |
This group keeps the usage of the contained JNDI environment
reference elements consistent across Java EE deployment descriptors.
Content: |
|
Includes: |
definitions of 10 elements |
Used: |
|
|
| javaee:resourceGroup |
This group collects elements that are common to all the
JNDI resource elements.
Content: |
|
Includes: |
definitions of 2 elements |
Used: |
|
|
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://java.sun.com/xml/ns/javaee" version="5" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:annotation>
<xsd:documentation>
@(#)javaee_5.xsds 1.65 06/02/17
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
The following definitions that appear in the common
shareable schema(s) of J2EE deployment descriptors should be
interpreted with respect to the context they are included:
Deployment Component may indicate one of the following:
j2ee application;
application client;
web application;
enterprise bean;
resource adapter;
Deployment File may indicate one of the following:
ear file;
war file;
jar file;
rar file;
</xsd:documentation>
</xsd:annotation>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This group keeps the usage of the contained description related
elements consistent across Java EE deployment descriptors.
All elements may occur multiple times with different languages,
to support localization of the content.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The description type is used by a description element to
provide text describing the parent element. The elements
that use this type should include any information that the
Deployment Component's Deployment File file producer wants
to provide to the consumer of the Deployment Component's
Deployment File (i.e., to the Deployer). Typically, the
tools used by such a Deployment File consumer will display
the description when processing the parent element that
contains the description.
The lang attribute defines the language that the
description is provided in. The default value is "en" (English).
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type defines a dewey decimal that is used
to describe versions of documents.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The display-name type contains a short name that is intended
to be displayed by tools. It is used by display-name
elements. The display name need not be unique.
Example:
...
<display-name xml:lang="en">
Employee Self Service
</display-name>
The value of the xml:lang attribute is "en" (English) by default.
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an EJB reference is linked to enterprise bean.
The value of the ejb-link element must be the ejb-name of an
enterprise bean in the same ejb-jar file or in another ejb-jar
file in the same Java EE application unit.
Alternatively, the name in the ejb-link element may be
composed of a path name specifying the ejb-jar containing the
referenced enterprise bean with the ejb-name of the target
bean appended and separated from the path name by "#". The
path name is relative to the Deployment File containing
Deployment Component that is referencing the enterprise
bean. This allows multiple enterprise beans with the same
ejb-name to be uniquely identified.
Examples:
<ejb-link>EmployeeRecord</ejb-link>
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The ejb-local-refType is used by ejb-local-ref elements for
the declaration of a reference to an enterprise bean's local
home or to the local business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of the Deployment
Component that's referencing the enterprise bean.
- the optional expected type of the referenced enterprise bean
- the optional expected local interface of the referenced
enterprise bean or the local business interface of the
referenced enterprise bean.
- the optional expected local home interface of the referenced
enterprise bean. Not applicable if this ejb-local-ref refers
to the local business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The ejb-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the
Deployment Component's environment and is relative to the
java:comp/env context. The name must be unique within the
Deployment Component.
It is recommended that name is prefixed with "ejb/".
Example:
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The ejb-ref-typeType contains the expected type of the
referenced enterprise bean.
The ejb-ref-type designates a value
that must be one of the following:
Entity
Session
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Entity"/>
<xsd:enumeration value="Session"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The ejb-refType is used by ejb-ref elements for the
declaration of a reference to an enterprise bean's home or
to the remote business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of
the Deployment Component that's referencing the enterprise
bean.
- the optional expected type of the referenced enterprise bean
- the optional remote interface of the referenced enterprise bean
or the remote business interface of the referenced enterprise
bean
- the optional expected home interface of the referenced
enterprise bean. Not applicable if this ejb-ref
refers to the remote business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type is used to designate an empty
element when used.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
The following are the legal values of env-entry-type-valuesType:
java.lang.Boolean
java.lang.Byte
java.lang.Character
java.lang.String
java.lang.Short
java.lang.Integer
java.lang.Long
java.lang.Float
java.lang.Double
Example:
<env-entry-type>java.lang.Boolean</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="java.lang.Boolean"/>
<xsd:enumeration value="java.lang.Byte"/>
<xsd:enumeration value="java.lang.Character"/>
<xsd:enumeration value="java.lang.String"/>
<xsd:enumeration value="java.lang.Short"/>
<xsd:enumeration value="java.lang.Integer"/>
<xsd:enumeration value="java.lang.Long"/>
<xsd:enumeration value="java.lang.Float"/>
<xsd:enumeration value="java.lang.Double"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The env-entryType is used to declare an application's
environment entry. The declaration consists of an optional
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
If a value is not specified and injection is requested,
no injection will occur and no entry of the specified name
will be created. This allows an initial value to be
specified in the source code without being incorrectly
changed when no override has been specified.
If a value is not specified and no injection is requested,
a value must be supplied during deployment.
This type is used by env-entry elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The elements that use this type designate the name of a
Java class or interface. The name is in the form of a
"binary name", as defined in the JLS. This is the form
of name used in Class.forName(). Tools that need the
canonical name (the name used in source code) will need
to convert this binary name to the canonical name.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type defines four different values which can designate
boolean values. This includes values yes and no which are
not designated by xsd:boolean
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="true"/>
<xsd:enumeration value="false"/>
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The homeType defines the fully-qualified name of
an enterprise bean's home interface.
Example:
<home>com.aardvark.payroll.PayrollHome</home>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The icon type contains small-icon and large-icon elements
that specify the file names for small and large GIF, JPEG,
or PNG icon images used to represent the parent element in a
GUI tool.
The xml:lang attribute defines the language that the
icon file names are provided in. Its value is "en" (English)
by default.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
An injection target specifies a class and a name within
that class into which a resource should be injected.
The injection target class specifies the fully qualified
class name that is the target of the injection. The
Java EE specifications describe which classes can be an
injection target.
The injection target name specifies the target within
the specified class. The target is first looked for as a
JavaBeans property name. If not found, the target is
looked for as a field name.
The specified resource will be injected into the target
during initialization of the class by either calling the
set method for the target property or by setting a value
into the named field.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The java-identifierType defines a Java identifier.
The users of this type should further verify that
the content does not contain Java reserved keywords.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This is a generic type that designates a Java primitive
type or a fully qualified name of a Java interface/type,
or an array of such types.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="[^\p{Z}]*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The jndi-nameType type designates a JNDI name in the
Deployment Component's environment and is relative to the
java:comp/env context. A JNDI name must be unique within the
Deployment Component.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This group keeps the usage of the contained JNDI environment
reference elements consistent across Java EE deployment descriptors.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The lifecycle-callback type specifies a method on a
class to be called when a lifecycle event occurs.
Note that each class may have only one lifecycle callback
method for any given event and that the method may not
be overloaded.
If the lifefycle-callback-class element is missing then
the class defining the callback is assumed to be the
component class in scope at the place in the descriptor
in which the callback definition appears.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The listenerType indicates the deployment properties for a web
application listener bean.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The localType defines the fully-qualified name of an
enterprise bean's local interface.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
The Assembler sets the value to reflect the flow of messages
between producers and consumers in the application.
The value must be the message-destination-name of a message
destination in the same Deployment File or in another
Deployment File in the same Java EE application unit.
Alternatively, the value may be composed of a path name
specifying a Deployment File containing the referenced
message destination with the message-destination-name of the
destination appended and separated from the path name by
"#". The path name is relative to the Deployment File
containing Deployment Component that is referencing the
message destination. This allows multiple message
destinations with the same name to be uniquely identified.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destination-ref element contains a declaration
of Deployment Component's reference to a message destination
associated with a resource in Deployment Component's
environment. It consists of:
- an optional description
- the message destination reference name
- an optional message destination type
- an optional specification as to whether
the destination is used for
consuming or producing messages, or both.
if not specified, "both" is assumed.
- an optional link to the message destination
- optional injection targets
The message destination type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Examples:
<message-destination-ref>
<message-destination-ref-name>jms/StockQueue
</message-destination-ref-name>
<message-destination-type>javax.jms.Queue
</message-destination-type>
<message-destination-usage>Consumes
</message-destination-usage>
<message-destination-link>CorporateStocks
</message-destination-link>
</message-destination-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destination-typeType specifies the type of
the destination. The type is specified by the Java interface
expected to be implemented by the destination.
Example:
<message-destination-type>javax.jms.Queue
</message-destination-type>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The message-destination-usageType specifies the use of the
message destination indicated by the reference. The value
indicates whether messages are consumed from the message
destination, produced for the destination, or both. The
Assembler makes use of this information in linking producers
of a destination with its consumers.
The value of the message-destination-usage element must be
one of the following:
Consumes
Produces
ConsumesProduces
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Consumes"/>
<xsd:enumeration value="Produces"/>
<xsd:enumeration value="ConsumesProduces"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destinationType specifies a message
destination. The logical destination described by this
element is mapped to a physical destination by the Deployer.
The message destination element contains:
- an optional description
- an optional display-name
- an optional icon
- a message destination name which must be unique
among message destination names within the same
Deployment File.
- an optional mapped name
Example:
<message-destination>
<message-destination-name>CorporateStocks
</message-destination-name>
</message-destination>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type is a general type that can be used to declare
parameter/value lists.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The param-name element contains the name of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The param-value element contains the value of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The elements that use this type designate either a relative
path or an absolute path starting with a "/".
In elements that specify a pathname to a file within the
same Deployment File, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the Deployment File's namespace. Absolute filenames (i.e.,
those starting with "/") also specify names in the root of
the Deployment File's namespace. In general, relative names
are preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The persistence-context-ref element contains a declaration
of Deployment Component's reference to a persistence context
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence context reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- an optional specification as to whether
the persistence context type is Transaction or
Extended. If not specified, Transaction is assumed.
- an optional list of persistence properties
- optional injection targets
Examples:
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
</persistence-context-ref>
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
<persistence-context-type>Extended</persistence-context-type>
</persistence-context-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The persistence-context-typeType specifies the transactional
nature of a persistence context reference.
The value of the persistence-context-type element must be
one of the following:
Transaction
Extended
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Transaction"/>
<xsd:enumeration value="Extended"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The persistence-unit-ref element contains a declaration
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence unit reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- optional injection targets
Examples:
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
</persistence-unit-ref>
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
</persistence-unit-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
Specifies a name/value pair.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:element>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
Example:
<remote>com.wombat.empl.EmployeeService</remote>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The res-authType specifies whether the Deployment Component
code signs on programmatically to the resource manager, or
whether the Container will sign on to the resource manager
on behalf of the Deployment Component. In the latter case,
the Container uses information that is supplied by the
Deployer.
The value must be one of the two following:
Application
Container
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Application"/>
<xsd:enumeration value="Container"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The res-sharing-scope type specifies whether connections
obtained through the given resource manager connection
factory reference can be shared. The value, if specified,
must be one of the two following:
Shareable
Unshareable
The default value is Shareable.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Shareable"/>
<xsd:enumeration value="Unshareable"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The resource-env-refType is used to define
resource-env-type elements. It contains a declaration of a
Deployment Component's reference to an administered object
associated with a resource in the Deployment Component's
environment. It consists of an optional description, the
resource environment reference name, and an optional
indication of the resource environment reference type
expected by the Deployment Component code.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The resource environment type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-env-ref>
<resource-env-ref-name>jms/StockQueue
</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue
</resource-env-ref-type>
</resource-env-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The resource-refType contains a declaration of a
Deployment Component's reference to an external resource. It
consists of an optional description, the resource manager
connection factory reference name, an optional indication of
the resource manager connection factory type expected by the
Deployment Component code, an optional type of authentication
(Application or Container), and an optional specification of
the shareability of connections obtained from the resource
(Shareable or Unshareable).
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The connection factory type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-ref>
<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference.
The name is a JNDI name relative to the
java:comp/env context.
The name must be unique within a Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This group collects elements that are common to all the
JNDI resource elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The role-nameType designates the name of a security role.
The name must conform to the lexical rules for a token.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The run-asType specifies the run-as identity to be
used for the execution of a component. It contains an
optional description, and the name of a security role.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The security-role-refType contains the declaration of a
security role reference in a component's or a
Deployment Component's code. The declaration consists of an
optional description, the security role name used in the
code, and an optional link to a security role. If the
security role is not specified, the Deployer must choose an
appropriate security role.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The security-roleType contains the definition of a security
role. The definition consists of an optional description of
the security role, and the security role name.
Example:
<security-role>
<description>
This role includes all employees who are authorized
to access the employee service application.
</description>
<role-name>employee</role-name>
</security-role>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:complexType name="string"> <xsd:annotation>
<xsd:documentation>
This is a special string datatype that is defined by Java EE as
a base type for defining collapsed strings. When schemas
require trailing/leading space elimination as well as
collapsing the existing whitespace, this base type may be
used.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:token">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This simple type designates a boolean with only two
permissible values
- true
- false
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="(true|false)"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The url-patternType contains the url pattern of the mapping.
It must follow the rules specified in Section 11.2 of the
Servlet API Specification. This pattern is assumed to be in
URL-decoded form and must not contain CR(#xD) or LF(#xA).
If it contains those characters, the container must inform
the developer with a descriptive error message.
The container must preserve all characters including whitespaces.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string"/>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:anyURI.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:anyURI">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:boolean.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:boolean">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:integer.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:integer">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:NMTOKEN.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:nonNegativeInteger.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:nonNegativeInteger">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:positiveInteger.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:positiveInteger">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:QName.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:QName">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:string.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
XML Schema "javaee_web_services_client_1_2.xsd"
Target Namespace:
-
Components:
-
Schema Location:
-
Included in Schema:
-
Annotation
Annotation 1:
@(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
Annotation 2:
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
Annotation 3:
(C) Copyright International Business Machines Corporation 2002
| Complex Type Summary |
| javaee:port-component-refType |
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:service-ref_handler-chainsType |
The handler-chains element defines the handlerchains associated with this
service or service endpoint.
Content: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:service-ref_handler-chainType |
The handler-chain element defines the handlerchain.
Content: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:service-ref_handlerType |
Declares the handler for a port-component.
Content: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
|
| javaee:service-refType |
The service-ref element declares a reference to a Web
service.
Content: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
|
| Simple Type Summary |
| javaee:service-ref_protocol-bindingListType |
Defines the type used for specifying a list of
protocol-bindingType(s).
|
| javaee:service-ref_protocol-bindingType |
Defines the type used for specifying the URI for the
protocol binding used by the port-component.
|
| javaee:service-ref_protocol-URIAliasType |
Defines the type that is used for specifying tokens that
start with ## which are used to alias existing standard
protocol bindings and support aliases for new standard
binding URIs that are introduced in future specifications.
|
| javaee:service-ref_qname-pattern |
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.
|
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://java.sun.com/xml/ns/javaee" version="1.2" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:annotation>
<xsd:documentation>
@(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
(C) Copyright International Business Machines Corporation 2002
</xsd:documentation>
</xsd:annotation>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-component-link element links a port-component-ref
to a specific port-component required to be made available
by a service reference.
The value of a port-component-link must be the
port-component-name of a port-component in the same module
or another module in the same application unit. The syntax
for specification follows the syntax defined for ejb-link
in the EJB 2.0 specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:sequence>
<xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The service-ref element declares a reference to a Web
service. It contains optional description, display name and
icons, a declaration of the required Service interface,
an optional WSDL document location, an optional set
of JAX-RPC mappings, an optional QName for the service element,
an optional set of Service Endpoint Interfaces to be resolved
by the container to a WSDL port, and an optional set of handlers.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-qname element declares the specific WSDL service
element that is being refered to. It is not specified if no
wsdl-file is declared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
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
choices are specified with the handler-chain element then the
handlers specified in the handler-chain will be applied on
everything.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice maxOccurs="1" minOccurs="0">
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The handler-chains element defines the handlerchains associated with this
service or service endpoint.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
Declares the handler for a port-component. Handlers can access the
init-param name/value pairs using the HandlerInfo interface. If
port-name is not specified, the handler is assumed to be associated
with all ports of the service.
Used in: service-ref
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Defines a fully qualified class name for the handler
implementation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Defines the QName of a SOAP header that will be processed
by the handler.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-name element defines the WSDL port-name that a
handler should be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
Defines the type that is used for specifying tokens that
start with ## which are used to alias existing standard
protocol bindings and support aliases for new standard
binding URIs that are introduced in future specifications.
The following tokens alias the standard protocol binding
URIs:
##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
##SOAP11_HTTP_MTOM =
"http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
##SOAP12_HTTP_MTOM =
"http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="##.+"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
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:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
Defines the type used for specifying the URI for the
protocol binding used by the port-component. For
portability one could use one of the following tokens that
alias the standard binding types:
##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:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This is used to specify the QName pattern in the
attribute service-name-pattern and port-name-pattern in
the handler-chain element
For example, the various forms acceptable here for
service-name-pattern attribute in handler-chain element
are :
Exact Name: service-name-pattern="ns1:EchoService"
In this case, handlers specified in this
handler-chain element will apply to all ports with
this exact service name. The namespace prefix must
have been declared in a namespace declaration
attribute in either the start-tag of the element
where the prefix is used or in an an ancestor
element (i.e. an element in whose content the
prefixed markup occurs)
Pattern : service-name-pattern="ns1:EchoService*"
In this case, handlers specified in this
handler-chain element will apply to all ports whose
Service names are like EchoService1, EchoServiceFoo
etc. The namespace prefix must have been declared in
a namespace declaration attribute in either the
start-tag of the element where the prefix is used or
in an an ancestor element (i.e. an element in whose
content the prefixed markup occurs)
Wild Card : service-name-pattern="*"
In this case, handlers specified in this handler-chain
element will apply to ports of all service names.
The same can be applied to port-name attribute in
handler-chain element.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
XML Schema "jsp_2_1.xsd"
Target Namespace:
-
Components:
-
Schema Location:
-
Includes Schema:
-
Included in Schema:
-
Annotation
Annotation 1:
@(#)jsp_2_1.xsds 1.5 08/11/05
Annotation 2:
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
Annotation 3:
This is the XML Schema for the JSP 2.1 deployment descriptor
types. The JSP 2.1 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-app_2_5.xsd
file to define JSP specific content.
Annotation 4:
The following conventions apply to all Java EE
deployment descriptor elements unless indicated otherwise.
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the JAR file's namespace. Absolute filenames (i.e., those
starting with "/") also specify names in the root of the
JAR file's namespace. In general, relative names are
preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
| Complex Type Summary |
| javaee:jsp-configType |
The jsp-configType is used to provide global configuration
information for the JSP files in a web application.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:jsp-fileType |
The jsp-file element contains the full path to a JSP file
within the web application beginning with a `/'.
|
| javaee:jsp-property-groupType |
The jsp-property-groupType is used to group a number of
files so they can be given global property information.
Content: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
|
| javaee:taglibType |
The taglibType defines the syntax for declaring in
the deployment descriptor that a tag library is
available to the application.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://java.sun.com/xml/ns/javaee" version="2.1" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:annotation>
<xsd:documentation>
@(#)jsp_2_1.xsds 1.5 08/11/05
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
This is the XML Schema for the JSP 2.1 deployment descriptor
types. The JSP 2.1 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-app_2_5.xsd
file to define JSP specific content.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
The following conventions apply to all Java EE
deployment descriptor elements unless indicated otherwise.
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the JAR file's namespace. Absolute filenames (i.e., those
starting with "/") also specify names in the root of the
JAR file's namespace. In general, relative names are
preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
</xsd:documentation>
</xsd:annotation>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
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>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The jsp-property-groupType is used to group a number of
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.
- Indicate that a resource is a JSP document (XML).
- Prelude and Coda automatic includes.
- Control whether the character sequence #{ is allowed
when used as a String literal.
- Control whether template text containing only
whitespaces must be removed from the response output.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
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>
<xsd:annotation>
<xsd:documentation>
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
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>
<xsd:annotation>
<xsd:documentation>
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
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>
<xsd:annotation>
<xsd:documentation>
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
<xsd:annotation>
<xsd:documentation>
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
<xsd:annotation>
<xsd:documentation>
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Indicates that template text containing only whitespaces
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The taglibType defines the syntax for declaring in
the deployment descriptor that a tag library is
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>
<xsd:annotation>
<xsd:documentation>
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
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>
<xsd:annotation>
<xsd:documentation>
the taglib-location element contains the location
(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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
</xsd:schema>
XML Schema "web-app_2_5.xsd"
Target Namespace:
-
Components:
-
Schema Location:
-
Includes Schemas (2):
-
Annotation
Annotation 1:
@(#)web-app_2_5.xsds 1.68 07/03/09
Annotation 2:
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
Annotation 3:
This is the XML Schema for the Servlet 2.5 deployment descriptor.
The deployment descriptor must be named "WEB-INF/web.xml" in the
web application's war file. All Servlet deployment descriptors
must indicate the web application schema by using the Java EE
namespace:
http://java.sun.com/xml/ns/javaee
and by indicating the version of the schema by
using the version element as shown below:
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="..."
version="2.5">
...
</web-app>
The instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for Java EE
namespace with the following location:
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
Annotation 4:
The following conventions apply to all Java EE
deployment descriptor elements unless indicated otherwise.
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the JAR file's namespace. Absolute filenames (i.e., those
starting with "/") also specify names in the root of the
JAR file's namespace. In general, relative names are
preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
| Complex Type Summary |
| javaee:auth-constraintType |
The auth-constraintType indicates the user roles that
should be permitted access to this resource
collection.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:auth-methodType |
The auth-methodType is used to configure the authentication
mechanism for the web application.
|
| javaee:dispatcherType |
The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
and ERROR.
|
| javaee:error-codeType |
The error-code contains an HTTP error code, ex: 404
Used in: error-page
Content: |
|
Includes: |
definition of 1 attribute |
Used: |
|
|
| javaee:error-pageType |
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:filter-mappingType |
Declaration of the filter mappings in this web
application is done by using filter-mappingType.
Content: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:filter-nameType |
The logical name of the filter is declare
by using filter-nameType.
|
| javaee:filterType |
The filterType is used to declare a filter in the web
application.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:form-login-configType |
The form-login-configType specifies the login and error
pages that should be used in form based login.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:locale-encoding-mapping-listType |
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
Content: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:locale-encoding-mappingType |
The locale-encoding-mapping contains locale name and
encoding name.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:login-configType |
The login-configType is used to configure the authentication
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
Content: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
|
| javaee:mime-mappingType |
The mime-mappingType defines a mapping between an extension
and a mime type.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:mime-typeType |
The mime-typeType is used to indicate a defined mime type.
|
| javaee:nonEmptyStringType |
This type defines a string which contains at least one
character.
|
| javaee:security-constraintType |
The security-constraintType is used to associate
security constraints with one or more web resource
collections
Used in: web-app
Content: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:servlet-mappingType |
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:servlet-nameType |
The servlet-name element contains the canonical name of the
servlet.
|
| javaee:servletType |
The servletType is used to declare a servlet.
Content: |
|
Includes: |
definitions of 1 attribute and 7 elements |
Used: |
|
|
| javaee:session-configType |
The session-configType defines the session parameters
for this web application.
Content: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
| javaee:transport-guaranteeType |
The transport-guaranteeType specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL.
|
| javaee:user-data-constraintType |
The user-data-constraintType is used to indicate how
data communicated between the client and container should be
protected.
Content: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
|
| javaee:war-pathType |
The elements that use this type designate a path starting
with a "/" and interpreted relative to the root of a WAR
file.
|
| javaee:web-appType |
Content: |
|
Includes: |
definitions of 3 attributes and 17 elements |
Used: |
|
|
| javaee:web-resource-collectionType |
The web-resource-collectionType is used to identify a subset
of the resources and HTTP methods on those resources within
a web application to which a security constraint applies.
Content: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
|
| javaee:welcome-file-listType |
The welcome-file-list contains an ordered list of welcome
files elements.
Content: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
|
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://java.sun.com/xml/ns/javaee" version="2.5" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:annotation>
<xsd:documentation>
@(#)web-app_2_5.xsds 1.68 07/03/09
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
Copyright 2003-2007 Sun Microsystems, Inc. All rights reserved.
The contents of this file are subject to the terms of either the
GNU General Public License Version 2 only ("GPL") or the Common
Development and Distribution License("CDDL") (collectively, the
"License"). You may not use this file except in compliance with
the License. You can obtain a copy of the License at
https://glassfish.dev.java.net/public/CDDL+GPL.html or
glassfish/bootstrap/legal/LICENSE.txt. See the License for the
specific language governing permissions and limitations under the
License.
When distributing the software, include this License Header
Notice in each file and include the License file at
glassfish/bootstrap/legal/LICENSE.txt. Sun designates this
particular file as subject to the "Classpath" exception as
provided by Sun in the GPL Version 2 section of the License file
that accompanied this code. If applicable, add the following
below the License Header, with the fields enclosed by brackets []
replaced by your own identifying information:
"Portions Copyrighted [year] [name of copyright owner]"
Contributor(s):
If you wish your version of this file to be governed by only the
CDDL or only the GPL Version 2, indicate your decision by adding
"[Contributor] elects to include this software in this
distribution under the [CDDL or GPL Version 2] license." If you
don't indicate a single choice of license, a recipient has the
option to distribute your version of this file under either the
CDDL, the GPL Version 2 or to extend the choice of license to its
licensees as provided above. However, if you add GPL Version 2
code and therefore, elected the GPL Version 2 license, then the
option applies only if the new code is made subject to such
option by the copyright holder.
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
This is the XML Schema for the Servlet 2.5 deployment descriptor.
The deployment descriptor must be named "WEB-INF/web.xml" in the
web application's war file. All Servlet deployment descriptors
must indicate the web application schema by using the Java EE
namespace:
http://java.sun.com/xml/ns/javaee
and by indicating the version of the schema by
using the version element as shown below:
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="..."
version="2.5">
...
</web-app>
The instance documents may indicate the published version of
the schema using the xsi:schemaLocation attribute for Java EE
namespace with the following location:
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:annotation>
<xsd:documentation>
The following conventions apply to all Java EE
deployment descriptor elements unless indicated otherwise.
- In elements that specify a pathname to a file within the
same JAR file, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the JAR file's namespace. Absolute filenames (i.e., those
starting with "/") also specify names in the root of the
JAR file's namespace. In general, relative names are
preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
</xsd:documentation>
</xsd:annotation>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The web-app element is the root of the deployment
descriptor for a web application. Note that the sub-elements
of this element can be in the arbitrary order. Because of
that, the multiplicity of the elements of distributable,
session-config, welcome-file-list, jsp-config, login-config,
and locale-encoding-mapping-list was changed from "?" to "*"
in this schema. However, the deployment descriptor instance
file must not contain multiple elements of session-config,
jsp-config, and login-config. When there are multiple elements of
welcome-file-list or locale-encoding-mapping-list, the container
must concatenate the element contents. The multiple occurence
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="web-app-servlet-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
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="javaee:servlet"/>
<xsd:field xpath="javaee:servlet-name"/>
</xsd:unique>
<xsd:unique name="web-app-filter-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
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="javaee:filter"/>
<xsd:field xpath="javaee:filter-name"/>
</xsd:unique>
<xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The ejb-local-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the web
application's environment and is relative to the
java:comp/env context. The name must be unique within
the web application.
It is recommended that name is prefixed with "ejb/".
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:ejb-local-ref"/>
<xsd:field xpath="javaee:ejb-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-ejb-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The ejb-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the 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="javaee:ejb-ref"/>
<xsd:field xpath="javaee:ejb-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-resource-env-ref-uniqueness">
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name of
a resource environment reference; its value is the
environment entry name used in the 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="javaee:resource-env-ref"/>
<xsd:field xpath="javaee:resource-env-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-message-destination-ref-uniqueness">
<xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies the name of
a message destination reference; its value is the
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="javaee:message-destination-ref"/>
<xsd:field xpath="javaee:message-destination-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-res-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference. The name
is a JNDI name relative to the java:comp/env context.
The name must be unique within a web application.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:resource-ref"/>
<xsd:field xpath="javaee:res-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-env-entry-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The env-entry-name element contains the name of a web
application's environment entry. The name is a JNDI
name relative to the java:comp/env context. The name
must be unique within a web application.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:env-entry"/>
<xsd:field xpath="javaee:env-entry-name"/>
</xsd:unique>
<xsd:key name="web-app-role-name-key">
<xsd:annotation>
<xsd:documentation>
A role-name-key is specified to allow the references
from the security-role-refs.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:security-role"/>
<xsd:field xpath="javaee:role-name"/>
</xsd:key>
<xsd:keyref name="web-app-role-name-references" refer="javaee:web-app-role-name-key">
<xsd:annotation>
<xsd:documentation>
The keyref indicates the references from
security-role-ref to a specified role-name.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:servlet/javaee:security-role-ref"/>
<xsd:field xpath="javaee:role-link"/>
</xsd:keyref>
</xsd:element>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The auth-constraintType indicates the user roles that
should be permitted access to this resource
collection. The role-name used here must either correspond
to the role-name of one of the security-role elements
defined for this web application, or be the specially
reserved role-name "*" that is a compact syntax for
indicating all roles in the web application. If both "*"
and rolenames appear, the container interprets this as all
roles. If no roles are defined, no user is allowed access
to the portion of the web application described by the
containing security-constraint. The container matches
role names case sensitively when determining access.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The auth-methodType is used to configure the authentication
mechanism for the web application. As a prerequisite to
gaining access to any web resources which are protected by
an authorization constraint, a user must have authenticated
using the configured mechanism. Legal values are "BASIC",
"DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
authentication scheme.
Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
and ERROR. A value of FORWARD means the Filter will be applied
under RequestDispatcher.forward() calls. A value of REQUEST
means the Filter will be applied under ordinary client calls to
the path or servlet. A value of INCLUDE means the Filter will be
applied under RequestDispatcher.include() calls. A value of
ERROR means the Filter will be applied under the error page
mechanism. The absence of any dispatcher elements in a
filter-mapping indicates a default of applying filters only under
ordinary client calls to the path or servlet.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="FORWARD"/>
<xsd:enumeration value="INCLUDE"/>
<xsd:enumeration value="REQUEST"/>
<xsd:enumeration value="ERROR"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The encodingType defines IANA character sets.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[^\s]+"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The error-code contains an HTTP error code, ex: 404
Used in: error-page
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="\d{3}"/>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
The exception-type contains a fully qualified class
name of a Java exception type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
<xsd:documentation>
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
Declaration of the filter mappings in this web
application is done by using filter-mappingType.
The container uses the filter-mapping
declarations to decide which filters to apply to a request,
and in what order. The container matches the request URI to
a Servlet in the normal way. To determine which filters to
apply it matches filter-mapping declarations either on
servlet-name, or on url-pattern for each filter-mapping
element, depending on which style is used. The order in
which filters are invoked is the order in which
filter-mapping declarations that match a request URI for a
servlet appear in the list of filter-mapping elements.The
filter-name value must be the value of the filter-name
sub-elements of one of the filter declarations in the
deployment descriptor.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice maxOccurs="unbounded" minOccurs="1">
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The logical name of the filter is declare
by using filter-nameType. This name is used to map the
filter. Each filter name is unique within the web
application.
Used in: filter, filter-mapping
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The filterType is used to declare a filter in the web
application. The filter is mapped to either a servlet or a
URL pattern in the filter-mapping element, using the
filter-name value to reference. Filters can access the
initialization parameters declared in the deployment
descriptor at runtime via the FilterConfig interface.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The fully qualified classname of the filter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The init-param element contains a name/value pair as
an initialization param of a servlet filter
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The form-login-configType specifies the login and error
pages that should be used in form based login. If form based
authentication is not used, these elements are ignored.
Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
A HTTP method type as defined in HTTP 1.1 section 2.2.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="[!-~-[\(\)<>@,;:"/\[\]?=\{\}\\\p{Z}]]+"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The locale-encoding-mapping contains locale name and
encoding name. The locale name must be either "Language-code",
such as "ja", defined by ISO-639 or "Language-code_Country-code",
such as "ja_JP". "Country code" is defined by ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The localeType defines valid locale defined by ISO-639-1
and ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The login-configType is used to configure the authentication
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The realm name element specifies the realm name to
use in HTTP Basic authorization.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The mime-mappingType defines a mapping between an extension
and a mime type.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The extension element contains a string describing an
extension. example: "txt"
</xsd:documentation>
</xsd:annotation>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The mime-typeType is used to indicate a defined mime type.
Example:
"text/plain"
Used in: mime-mapping
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type defines a string which contains at least one
character.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:minLength value="1"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:restriction base="xsd:string">
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The servlet-name element contains the canonical name of the
servlet. Each servlet name is unique within the web
application.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The servletType is used to declare a servlet.
It contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup
element is present, then the JSP should be precompiled and
loaded.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
The servlet-class element contains the fully
qualified class name of the servlet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
<xsd:documentation>
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The session-configType defines the session parameters
for this web application.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The transport-guaranteeType specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL. NONE means that the application does not
require any transport guarantees. A value of INTEGRAL means
that the application requires that the data sent between the
client and server be sent in such a way that it can't be
changed in transit. CONFIDENTIAL means that the application
requires that the data be transmitted in a fashion that
prevents other entities from observing the contents of the
transmission. In most cases, the presence of the INTEGRAL or
CONFIDENTIAL flag will indicate that the use of SSL is
required.
Used in: user-data-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="NONE"/>
<xsd:enumeration value="INTEGRAL"/>
<xsd:enumeration value="CONFIDENTIAL"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The user-data-constraintType is used to indicate how
data communicated between the client and container should be
protected.
Used in: security-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The elements that use this type designate a path starting
with a "/" and interpreted relative to the root of a WAR
file.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="/.*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
This type contains the recognized versions of
web-application supported. It is used to designate the
version of the web application.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="2.5"/>
</xsd:restriction>
</xsd:simpleType>
<!-- **************************************************** -->
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:attribute name="id" type="xsd:ID"/> <xsd:annotation>
<xsd:documentation>
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The web-resource-collectionType is used to identify a subset
of the resources and HTTP methods on those resources within
a web application to which a security constraint applies. If
no HTTP methods are specified, then the security constraint
applies to all HTTP methods.
Used in: security-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The web-resource-name contains the name of this web
resource collection.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
<!-- **************************************************** -->
<xsd:annotation>
<xsd:documentation>
The welcome-file-list contains an ordered list of welcome
files elements.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="welcome-file" type="xsd:string"> <xsd:annotation>
<xsd:documentation>
The welcome-file element contains file name to use
as a default welcome file, such as index.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
</xsd:schema>
element <javaee:auth-constraint>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:auth-constraint |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:auth-constraint> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:auth-method>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:auth-method |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:auth-method> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:context-param>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:context-param |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:context-param> |
May contain elements (3):
-
May be included in elements (1):
-
Usage / Definition Locations
Annotation
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The param-name element contains the name of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-name element contains the name of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The param-value element contains the value of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-value element contains the value of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:deferred-syntax-allowed-as-literal>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:deferred-syntax-allowed-as-literal |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:deferred-syntax-allowed-as-literal> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:description>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:description |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </javaee:description> |
May be included in elements (24):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
element <javaee:dispatcher>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:dispatcher |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "FORWARD" | "INCLUDE" | "REQUEST" | "ERROR" } |
|
| </javaee:dispatcher> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:display-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:display-name |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </javaee:display-name> |
May be included in elements (9):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
element <javaee:distributable>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:distributable |
| |
id |
= |
xsd:ID |
| /> |
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:ejb-link>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:ejb-link |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:ejb-link> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:ejb-local-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:ejb-local-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:ejb-local-ref> |
May contain elements (8):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:ejb-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:ejb-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:ejb-ref> |
May contain elements (8):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
element <javaee:ejb-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:ejb-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:ejb-ref-name> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:ejb-ref-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:ejb-ref-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Entity" | "Session" } |
|
| </javaee:ejb-ref-type> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:el-ignored>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:el-ignored |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:el-ignored> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
EL evaluation is enabled for Web Applications using
a Servlet 2.4 or greater web.xml, and disabled
otherwise.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:enable-mtom>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:enable-mtom |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:enable-mtom> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:encoding>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:encoding> |
| |
Content: |
{ xsd:string } |
| </javaee:encoding> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:env-entry>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:env-entry |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:env-entry> |
May contain elements (6):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:env-entry-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:env-entry-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:env-entry-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:env-entry-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:env-entry-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "java.lang.Boolean" | "java.lang.Byte" | "java.lang.Character" | "java.lang.String" | "java.lang.Short" | "java.lang.Integer" | "java.lang.Long" | "java.lang.Float" | "java.lang.Double" } |
|
| </javaee:env-entry-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:env-entry-value>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:env-entry-value |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:env-entry-value> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:error-code>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:error-code |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ xsd:positiveInteger } |
|
| </javaee:error-code> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:error-page>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:error-page |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:error-page> |
May contain elements (3):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The exception-type contains a fully qualified class
name of a Java exception type.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The exception-type contains a fully qualified class
name of a Java exception type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:exception-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:exception-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:exception-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The exception-type contains a fully qualified class
name of a Java exception type.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:extension>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:extension |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:extension> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:filter>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:filter |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:filter> |
May contain elements (6):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The fully qualified classname of the filter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The fully qualified classname of the filter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The init-param element contains a name/value pair as
an initialization param of a servlet filter
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The init-param element contains a name/value pair as
an initialization param of a servlet filter
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:filter-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:filter-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:filter-class> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The fully qualified classname of the filter.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:filter-mapping>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:filter-mapping |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:filter-mapping> |
May contain elements (4):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:filter-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:filter-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:filter-name> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:form-error-page>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:form-error-page |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:form-error-page> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:form-login-config>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:form-login-config |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:form-login-config> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:form-login-page>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:form-login-page |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:form-login-page> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:handler>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:handler |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:handler> |
May contain elements (9):
-
May be included in elements (2):
-
Usage / Definition Locations
Annotation
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Defines a fully qualified class name for the handler
implementation.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines a fully qualified class name for the handler
implementation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Defines the name of the handler. The name must be unique
within the module.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The port-name element defines the WSDL port-name that a
handler should be associated with.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-name element defines the WSDL port-name that a
handler should be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Defines the QName of a SOAP header that will be processed
by the handler.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the QName of a SOAP header that will be processed
by the handler.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:handler-chain>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:handler-chain |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:handler-chain> |
May contain elements (4):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:handler-chains>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:handler-chains |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:handler-chains> |
May contain elements (1):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
To be used with JAX-WS based runtime only.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
element <javaee:handler-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:handler-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:handler-class> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Defines a fully qualified class name for the handler
implementation.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:handler-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:handler-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:handler-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Defines the name of the handler. The name must be unique
within the module.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:home>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:home |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:home> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:http-method>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:http-method> |
| |
Content: |
{ xsd:token } |
| </javaee:http-method> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:icon>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:icon |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </javaee:icon> |
May contain elements (2):
-
May be included in elements (8):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
Content Element Detail
-
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:include-coda>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:include-coda |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:include-coda> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the end of each
JSP page in this jsp-property-group.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:include-prelude>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:include-prelude |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:include-prelude> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the beginning of each
JSP page in this jsp-property-group.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:init-param>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:init-param |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:init-param> |
May contain elements (3):
-
May be included in elements (3):
-
Usage / Definition Locations
Annotation
The init-param element contains a name/value pair as
an initialization param of a servlet filter
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The param-name element contains the name of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-name element contains the name of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The param-value element contains the value of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-value element contains the value of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:injection-target>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:injection-target> |
| |
|
| </javaee:injection-target> |
May contain elements (2):
-
May be included in elements (9):
-
Usage / Definition Locations
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:injection-target-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:injection-target-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:injection-target-class> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:injection-target-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:injection-target-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:injection-target-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:is-xml>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:is-xml |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:is-xml> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
If false, the resources are assumed to not
be JSP documents, unless there is another
property group that indicates otherwise.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:jaxrpc-mapping-file>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:jaxrpc-mapping-file |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:jaxrpc-mapping-file> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:jsp-config>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:jsp-config |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:jsp-config> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:jsp-file>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:jsp-file |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:jsp-file> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:jsp-property-group>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:jsp-property-group |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
javaee:description*, javaee:display-name*, javaee:icon*, javaee:url-pattern+, javaee:el-ignored?, javaee:page-encoding?, javaee:scripting-invalid?, javaee:is-xml?, javaee:include-prelude*, javaee:include-coda*, javaee:deferred-syntax-allowed-as-literal?, javaee:trim-directive-whitespaces? |
|
| </javaee:jsp-property-group> |
May contain elements (12):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
EL evaluation is enabled for Web Applications using
a Servlet 2.4 or greater web.xml, and disabled
otherwise.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
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>
-
XML Source (see within schema source)
-
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the end of each
JSP page in this jsp-property-group.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
-
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the beginning of each
JSP page in this jsp-property-group.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
-
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
If false, the resources are assumed to not
be JSP documents, unless there is another
property group that indicates otherwise.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
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>
-
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
in a JSP configuration element matching the document.
It is legal to name the same encoding through
mulitple mechanisms.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
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>
-
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Indicates that template text containing only whitespaces
must be removed from the response output. It has no
effect on JSP documents (XML syntax). Disabled (false)
by default.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Indicates that template text containing only whitespaces
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>
-
XML Source (see within schema source)
element <javaee:large-icon>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:large-icon |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:large-icon> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:lifecycle-callback-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:lifecycle-callback-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:lifecycle-callback-class> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:lifecycle-callback-method>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:lifecycle-callback-method |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:lifecycle-callback-method> |
May be included in elements (2):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:listener>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:listener |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:listener> |
May contain elements (4):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:listener-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:listener-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:listener-class> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:load-on-startup>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:load-on-startup> |
| |
Content: |
{ "" | xsd:integer } |
| </javaee:load-on-startup> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
element <javaee:local>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:local |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:local> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:local-home>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:local-home |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:local-home> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:locale>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:locale> |
| |
Content: |
{ xsd:string } |
| </javaee:locale> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:locale-encoding-mapping>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:locale-encoding-mapping |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:locale-encoding-mapping> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:locale-encoding-mapping-list>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:locale-encoding-mapping-list |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:locale-encoding-mapping-list> |
May contain elements (1):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
element <javaee:location>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:location |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:location> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:login-config>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:login-config |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:login-config> |
May contain elements (3):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The realm name element specifies the realm name to
use in HTTP Basic authorization.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The realm name element specifies the realm name to
use in HTTP Basic authorization.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:mapped-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:mapped-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:mapped-name> |
May be included in elements (10):
-
Usage / Definition Locations
Annotation
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:message-destination>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination> |
May contain elements (5):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:message-destination-link>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-link |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination-link> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:message-destination-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:message-destination-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination-ref> |
May contain elements (7):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:message-destination-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:message-destination-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:message-destination-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:message-destination-usage>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:message-destination-usage |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Consumes" | "Produces" | "ConsumesProduces" } |
|
| </javaee:message-destination-usage> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:mime-mapping>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:mime-mapping |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:mime-mapping> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:mime-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:mime-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:mime-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:page-encoding>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:page-encoding |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:page-encoding> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
in a JSP configuration element matching the document.
It is legal to name the same encoding through
mulitple mechanisms.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:param-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:param-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:param-name> |
May be included in elements (2):
-
Usage / Definition Locations
Annotation
The param-name element contains the name of a
parameter.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:param-value>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:param-value |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:param-value> |
May be included in elements (2):
-
Usage / Definition Locations
Annotation
The param-value element contains the value of a
parameter.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:persistence-context-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-context-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-context-ref> |
May contain elements (7):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:persistence-context-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-context-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-context-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:persistence-context-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-context-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Transaction" | "Extended" } |
|
| </javaee:persistence-context-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:persistence-property>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-property |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-property> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source) </xsd:element>
-
XML Source (see within schema source) </xsd:element>
element <javaee:persistence-unit-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-unit-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-unit-name> |
May be included in elements (2):
-
Usage / Definition Locations
Annotation
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:persistence-unit-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-unit-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-unit-ref> |
May contain elements (5):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:persistence-unit-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:persistence-unit-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:persistence-unit-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:port-component-link>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:port-component-link |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:port-component-link> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
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.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:port-component-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:port-component-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:port-component-ref> |
May contain elements (3):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-component-link element links a port-component-ref
to a specific port-component required to be made available
by a service reference.
The value of a port-component-link must be the
port-component-name of a port-component in the same module
or another module in the same application unit. The syntax
for specification follows the syntax defined for ejb-link
in the EJB 2.0 specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:port-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:port-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:port-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The port-name element defines the WSDL port-name that a
handler should be associated with.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:port-name-pattern>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:port-name-pattern> |
| |
Content: |
{ xsd:token } |
| </javaee:port-name-pattern> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:post-construct>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:post-construct> |
| |
|
| </javaee:post-construct> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:pre-destroy>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:pre-destroy> |
| |
|
| </javaee:pre-destroy> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:protocol-bindings>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:protocol-bindings> |
| |
Content: |
{ list of (xsd:anyURI | xsd:token) } |
| </javaee:protocol-bindings> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:realm-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:realm-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:realm-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The realm name element specifies the realm name to
use in HTTP Basic authorization.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:remote>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:remote |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:remote> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:res-auth>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:res-auth |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Application" | "Container" } |
|
| </javaee:res-auth> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:res-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:res-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:res-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
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.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:res-sharing-scope>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:res-sharing-scope |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Shareable" | "Unshareable" } |
|
| </javaee:res-sharing-scope> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:res-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:res-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:res-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:resource-env-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:resource-env-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:resource-env-ref> |
May contain elements (5):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:resource-env-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:resource-env-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:resource-env-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:resource-env-ref-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:resource-env-ref-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:resource-env-ref-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:resource-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:resource-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:resource-ref> |
May contain elements (7):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference.
The name is a JNDI name relative to the
java:comp/env context.
The name must be unique within a Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:role-link>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:role-link |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:role-link> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:role-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:role-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:role-name> |
May be included in elements (4):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:run-as>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:run-as |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:run-as> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:scripting-invalid>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:scripting-invalid |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:scripting-invalid> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:security-constraint>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:security-constraint |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:security-constraint> |
May contain elements (4):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:security-role>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:security-role |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:security-role> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:security-role-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:security-role-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:security-role-ref> |
May contain elements (3):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:service-endpoint-interface>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-endpoint-interface |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:service-endpoint-interface> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:service-interface>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-interface |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:service-interface> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:service-name-pattern>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:service-name-pattern> |
| |
Content: |
{ xsd:token } |
| </javaee:service-name-pattern> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
element <javaee:service-qname>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-qname |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:service-qname> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
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.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:service-ref>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-ref |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
javaee:description*, javaee:display-name*, javaee:icon*, javaee:service-ref-name, javaee:service-interface, javaee:service-ref-type?, javaee:wsdl-file?, javaee:jaxrpc-mapping-file?, javaee:service-qname?, javaee:port-component-ref*, (javaee:handler* | javaee:handler-chains?), javaee:mapped-name?, javaee:injection-target* |
|
| </javaee:service-ref> |
May contain elements (14):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
To be used with JAX-WS based runtime only.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-qname element declares the specific WSDL service
element that is being refered to. It is not specified if no
wsdl-file is declared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:service-ref-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-ref-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:service-ref-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:service-ref-type>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:service-ref-type |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:service-ref-type> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:servlet>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:servlet |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:servlet> |
May contain elements (10):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The servlet-class element contains the fully
qualified class name of the servlet.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The servlet-class element contains the fully
qualified class name of the servlet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
element <javaee:servlet-class>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:servlet-class |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:servlet-class> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The servlet-class element contains the fully
qualified class name of the servlet.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:servlet-mapping>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:servlet-mapping |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:servlet-mapping> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:servlet-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:servlet-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:servlet-name> |
May be included in elements (3):
-
Usage / Definition Locations
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:session-config>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:session-config |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:session-config> |
May contain elements (1):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:session-timeout>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:session-timeout |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:session-timeout> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:small-icon>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:small-icon |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:small-icon> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:soap-header>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:soap-header |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:soap-header> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Defines the QName of a SOAP header that will be processed
by the handler.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:soap-role>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:soap-role |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:soap-role> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:taglib>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:taglib |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:taglib> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
the taglib-location element contains the location
(as a resource relative to the root of the web
application) where to find the Tag Library
Description file for the tag library.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
the taglib-location element contains the location
(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>
-
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
absolute URI specification, or a relative URI.
There should be no entries in web.xml with the
same taglib-uri value.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
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>
element <javaee:taglib-location>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:taglib-location |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:taglib-location> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
the taglib-location element contains the location
(as a resource relative to the root of the web
application) where to find the Tag Library
Description file for the tag library.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:taglib-uri>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:taglib-uri |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:taglib-uri> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
absolute URI specification, or a relative URI.
There should be no entries in web.xml with the
same taglib-uri value.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:transport-guarantee>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:transport-guarantee |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "NONE" | "INTEGRAL" | "CONFIDENTIAL" } |
|
| </javaee:transport-guarantee> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:trim-directive-whitespaces>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:trim-directive-whitespaces |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:trim-directive-whitespaces> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
Indicates that template text containing only whitespaces
must be removed from the response output. It has no
effect on JSP documents (XML syntax). Disabled (false)
by default.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:url-pattern>
Namespace: |
|
Type: |
|
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:url-pattern> |
| |
|
| </javaee:url-pattern> |
May be included in elements (4):
-
Usage / Definition Locations
element <javaee:user-data-constraint>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:user-data-constraint |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:user-data-constraint> |
May contain elements (2):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:value>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:value |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:value> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:web-app>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
Used: |
never |
| XML Representation Summary |
| <javaee:web-app |
| |
id |
= |
xsd:ID |
| |
metadata-complete |
= |
xsd:boolean |
| |
version |
= |
"2.5" |
| |
> |
| |
Content: |
((javaee:description*, javaee:display-name*, javaee:icon*) | javaee:distributable | javaee:context-param | javaee:filter | javaee:filter-mapping | javaee:listener | javaee:servlet | javaee:servlet-mapping | javaee:session-config | javaee:mime-mapping | javaee:welcome-file-list | javaee:error-page | javaee:jsp-config | javaee:security-constraint | javaee:login-config | javaee:security-role | (javaee:env-entry*, javaee:ejb-ref*, javaee:ejb-local-ref*, javaee:service-ref*, javaee:resource-ref*, javaee:resource-env-ref*, javaee:message-destination-ref*, javaee:persistence-context-ref*, javaee:persistence-unit-ref*, javaee:post-construct*, javaee:pre-destroy*) | javaee:message-destination | javaee:locale-encoding-mapping-list)* |
|
| </javaee:web-app> |
May contain elements (31):
-
Annotation
The web-app element is the root of the deployment
descriptor for a web application. Note that the sub-elements
of this element can be in the arbitrary order. Because of
that, the multiplicity of the elements of distributable,
session-config, welcome-file-list, jsp-config, login-config,
and locale-encoding-mapping-list was changed from "?" to "*"
in this schema. However, the deployment descriptor instance
file must not contain multiple elements of session-config,
jsp-config, and login-config. When there are multiple elements of
welcome-file-list or locale-encoding-mapping-list, the container
must concatenate the element contents. The multiple occurence
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The web-app element is the root of the deployment
descriptor for a web application. Note that the sub-elements
of this element can be in the arbitrary order. Because of
that, the multiplicity of the elements of distributable,
session-config, welcome-file-list, jsp-config, login-config,
and locale-encoding-mapping-list was changed from "?" to "*"
in this schema. However, the deployment descriptor instance
file must not contain multiple elements of session-config,
jsp-config, and login-config. When there are multiple elements of
welcome-file-list or locale-encoding-mapping-list, the container
must concatenate the element contents. The multiple occurence
of the element distributable is redundant and the container
treats that case exactly in the same way when there is only
one distributable.
</xsd:documentation>
</xsd:annotation>
<xsd:unique name="web-app-servlet-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
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="javaee:servlet"/>
<xsd:field xpath="javaee:servlet-name"/>
</xsd:unique>
<xsd:unique name="web-app-filter-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
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="javaee:filter"/>
<xsd:field xpath="javaee:filter-name"/>
</xsd:unique>
<xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The ejb-local-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the web
application's environment and is relative to the
java:comp/env context. The name must be unique within
the web application.
It is recommended that name is prefixed with "ejb/".
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:ejb-local-ref"/>
<xsd:field xpath="javaee:ejb-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-ejb-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The ejb-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the 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="javaee:ejb-ref"/>
<xsd:field xpath="javaee:ejb-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-resource-env-ref-uniqueness">
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name of
a resource environment reference; its value is the
environment entry name used in the 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="javaee:resource-env-ref"/>
<xsd:field xpath="javaee:resource-env-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-message-destination-ref-uniqueness">
<xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies the name of
a message destination reference; its value is the
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="javaee:message-destination-ref"/>
<xsd:field xpath="javaee:message-destination-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-res-ref-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference. The name
is a JNDI name relative to the java:comp/env context.
The name must be unique within a web application.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:resource-ref"/>
<xsd:field xpath="javaee:res-ref-name"/>
</xsd:unique>
<xsd:unique name="web-app-env-entry-name-uniqueness">
<xsd:annotation>
<xsd:documentation>
The env-entry-name element contains the name of a web
application's environment entry. The name is a JNDI
name relative to the java:comp/env context. The name
must be unique within a web application.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:env-entry"/>
<xsd:field xpath="javaee:env-entry-name"/>
</xsd:unique>
<xsd:key name="web-app-role-name-key">
<xsd:annotation>
<xsd:documentation>
A role-name-key is specified to allow the references
from the security-role-refs.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:security-role"/>
<xsd:field xpath="javaee:role-name"/>
</xsd:key>
<xsd:keyref name="web-app-role-name-references" refer="javaee:web-app-role-name-key">
<xsd:annotation>
<xsd:documentation>
The keyref indicates the references from
security-role-ref to a specified role-name.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:servlet/javaee:security-role-ref"/>
<xsd:field xpath="javaee:role-link"/>
</xsd:keyref>
</xsd:element>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
metadata-complete
-
Type: |
xsd:boolean, predefined |
Use: |
optional |
Defined: |
|
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
version
-
Type: |
|
Use: |
required |
Defined: |
|
XML Source (see within schema source)
Content Element Detail
-
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source) <xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
element <javaee:web-resource-collection>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:web-resource-collection |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:web-resource-collection> |
May contain elements (4):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The web-resource-name contains the name of this web
resource collection.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The web-resource-name contains the name of this web
resource collection.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:web-resource-name>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:web-resource-name |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:web-resource-name> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The web-resource-name contains the name of this web
resource collection.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
element <javaee:welcome-file>
Namespace: |
|
Type: |
xsd:string |
Content: |
simple |
Defined: |
|
| XML Representation Summary |
| <javaee:welcome-file> |
| |
Content: |
{ xsd:string } |
| </javaee:welcome-file> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The welcome-file element contains file name to use
as a default welcome file, such as index.html
element <javaee:welcome-file-list>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:welcome-file-list |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:welcome-file-list> |
May contain elements (1):
-
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
Type: |
xsd:string, predefined, simple content |
Defined: |
|
The welcome-file element contains file name to use
as a default welcome file, such as index.html
XML Source (see within schema source) <xsd:element maxOccurs="unbounded" name="welcome-file" type="xsd:string"> <xsd:annotation>
<xsd:documentation>
The welcome-file element contains file name to use
as a default welcome file, such as index.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
element <javaee:wsdl-file>
Namespace: |
|
Type: |
|
Content: |
|
Defined: |
|
| XML Representation Summary |
| <javaee:wsdl-file |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </javaee:wsdl-file> |
May be included in elements (1):
-
Usage / Definition Locations
- Within global complexTypes (1):
Annotation
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:auth-constraintType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The auth-constraintType indicates the user roles that
should be permitted access to this resource
collection. The role-name used here must either correspond
to the role-name of one of the security-role elements
defined for this web application, or be the specially
reserved role-name "*" that is a compact syntax for
indicating all roles in the web application. If both "*"
and rolenames appear, the container interprets this as all
roles. If no roles are defined, no user is allowed access
to the portion of the web application described by the
containing security-constraint. The container matches
role names case sensitively when determining access.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The auth-constraintType indicates the user roles that
should be permitted access to this resource
collection. The role-name used here must either correspond
to the role-name of one of the security-role elements
defined for this web application, or be the specially
reserved role-name "*" that is a compact syntax for
indicating all roles in the web application. If both "*"
and rolenames appear, the container interprets this as all
roles. If no roles are defined, no user is allowed access
to the portion of the web application described by the
containing security-constraint. The container matches
role names case sensitively when determining access.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:auth-methodType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The auth-methodType is used to configure the authentication
mechanism for the web application. As a prerequisite to
gaining access to any web resources which are protected by
an authorization constraint, a user must have authenticated
using the configured mechanism. Legal values are "BASIC",
"DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
authentication scheme.
Used in: login-config
Type Definition Detail
| Type Derivation Tree xsd:token javaee:auth-methodType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The auth-methodType is used to configure the authentication
mechanism for the web application. As a prerequisite to
gaining access to any web resources which are protected by
an authorization constraint, a user must have authenticated
using the configured mechanism. Legal values are "BASIC",
"DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
authentication scheme.
Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:descriptionType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The description type is used by a description element to
provide text describing the parent element. The elements
that use this type should include any information that the
Deployment Component's Deployment File file producer wants
to provide to the consumer of the Deployment Component's
Deployment File (i.e., to the Deployer). Typically, the
tools used by such a Deployment File consumer will display
the description when processing the parent element that
contains the description.
The lang attribute defines the language that the
description is provided in. The default value is "en" (English).
Type Definition Detail
| Type Derivation Tree xsd:string javaee:descriptionType (extension) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The description type is used by a description element to
provide text describing the parent element. The elements
that use this type should include any information that the
Deployment Component's Deployment File file producer wants
to provide to the consumer of the Deployment Component's
Deployment File (i.e., to the Deployer). Typically, the
tools used by such a Deployment File consumer will display
the description when processing the parent element that
contains the description.
The lang attribute defines the language that the
description is provided in. The default value is "en" (English).
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
complexType "javaee:dispatcherType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "FORWARD" | "INCLUDE" | "REQUEST" | "ERROR" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
and ERROR. A value of FORWARD means the Filter will be applied
under RequestDispatcher.forward() calls. A value of REQUEST
means the Filter will be applied under ordinary client calls to
the path or servlet. A value of INCLUDE means the Filter will be
applied under RequestDispatcher.include() calls. A value of
ERROR means the Filter will be applied under the error page
mechanism. The absence of any dispatcher elements in a
filter-mapping indicates a default of applying filters only under
ordinary client calls to the path or servlet.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:dispatcherType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"FORWARD", "INCLUDE", "REQUEST", "ERROR" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
and ERROR. A value of FORWARD means the Filter will be applied
under RequestDispatcher.forward() calls. A value of REQUEST
means the Filter will be applied under ordinary client calls to
the path or servlet. A value of INCLUDE means the Filter will be
applied under RequestDispatcher.include() calls. A value of
ERROR means the Filter will be applied under the error page
mechanism. The absence of any dispatcher elements in a
filter-mapping indicates a default of applying filters only under
ordinary client calls to the path or servlet.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="FORWARD"/>
<xsd:enumeration value="INCLUDE"/>
<xsd:enumeration value="REQUEST"/>
<xsd:enumeration value="ERROR"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:display-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The display-name type contains a short name that is intended
to be displayed by tools. It is used by display-name
elements. The display name need not be unique.
Example:
...
<display-name xml:lang="en">
Employee Self Service
</display-name>
The value of the xml:lang attribute is "en" (English) by default.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:display-nameType (extension) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The display-name type contains a short name that is intended
to be displayed by tools. It is used by display-name
elements. The display name need not be unique.
Example:
...
<display-name xml:lang="en">
Employee Self Service
</display-name>
The value of the xml:lang attribute is "en" (English) by default.
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
complexType "javaee:ejb-linkType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an EJB reference is linked to enterprise bean.
The value of the ejb-link element must be the ejb-name of an
enterprise bean in the same ejb-jar file or in another ejb-jar
file in the same Java EE application unit.
Alternatively, the name in the ejb-link element may be
composed of a path name specifying the ejb-jar containing the
referenced enterprise bean with the ejb-name of the target
bean appended and separated from the path name by "#". The
path name is relative to the Deployment File containing
Deployment Component that is referencing the enterprise
bean. This allows multiple enterprise beans with the same
ejb-name to be uniquely identified.
Examples:
<ejb-link>EmployeeRecord</ejb-link>
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:ejb-linkType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The ejb-linkType is used by ejb-link
elements in the ejb-ref or ejb-local-ref elements to specify
that an EJB reference is linked to enterprise bean.
The value of the ejb-link element must be the ejb-name of an
enterprise bean in the same ejb-jar file or in another ejb-jar
file in the same Java EE application unit.
Alternatively, the name in the ejb-link element may be
composed of a path name specifying the ejb-jar containing the
referenced enterprise bean with the ejb-name of the target
bean appended and separated from the path name by "#". The
path name is relative to the Deployment File containing
Deployment Component that is referencing the enterprise
bean. This allows multiple enterprise beans with the same
ejb-name to be uniquely identified.
Examples:
<ejb-link>EmployeeRecord</ejb-link>
<ejb-link>../products/product.jar#ProductEJB</ejb-link>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:ejb-local-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (8):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The ejb-local-refType is used by ejb-local-ref elements for
the declaration of a reference to an enterprise bean's local
home or to the local business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of the Deployment
Component that's referencing the enterprise bean.
- the optional expected type of the referenced enterprise bean
- the optional expected local interface of the referenced
enterprise bean or the local business interface of the
referenced enterprise bean.
- the optional expected local home interface of the referenced
enterprise bean. Not applicable if this ejb-local-ref refers
to the local business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The ejb-local-refType is used by ejb-local-ref elements for
the declaration of a reference to an enterprise bean's local
home or to the local business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of the Deployment
Component that's referencing the enterprise bean.
- the optional expected type of the referenced enterprise bean
- the optional expected local interface of the referenced
enterprise bean or the local business interface of the
referenced enterprise bean.
- the optional expected local home interface of the referenced
enterprise bean. Not applicable if this ejb-local-ref refers
to the local business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:ejb-ref-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The ejb-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the
Deployment Component's environment and is relative to the
java:comp/env context. The name must be unique within the
Deployment Component.
It is recommended that name is prefixed with "ejb/".
Example:
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:ejb-ref-nameType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The ejb-ref-name element contains the name of an EJB
reference. The EJB reference is an entry in the
Deployment Component's environment and is relative to the
java:comp/env context. The name must be unique within the
Deployment Component.
It is recommended that name is prefixed with "ejb/".
Example:
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:ejb-ref-typeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Entity" | "Session" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
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
Type Definition Detail
| Type Derivation Tree xsd:token javaee:ejb-ref-typeType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"Entity", "Session" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The ejb-ref-typeType contains the expected type of the
referenced enterprise bean.
The ejb-ref-type designates a value
that must be one of the following:
Entity
Session
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Entity"/>
<xsd:enumeration value="Session"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:ejb-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (8):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The ejb-refType is used by ejb-ref elements for the
declaration of a reference to an enterprise bean's home or
to the remote business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of
the Deployment Component that's referencing the enterprise
bean.
- the optional expected type of the referenced enterprise bean
- the optional remote interface of the referenced enterprise bean
or the remote business interface of the referenced enterprise
bean
- the optional expected home interface of the referenced
enterprise bean. Not applicable if this ejb-ref
refers to the remote business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The ejb-refType is used by ejb-ref elements for the
declaration of a reference to an enterprise bean's home or
to the remote business interface of a 3.0 bean.
The declaration consists of:
- an optional description
- the EJB reference name used in the code of
the Deployment Component that's referencing the enterprise
bean.
- the optional expected type of the referenced enterprise bean
- the optional remote interface of the referenced enterprise bean
or the remote business interface of the referenced enterprise
bean
- the optional expected home interface of the referenced
enterprise bean. Not applicable if this ejb-ref
refers to the remote business interface of a 3.0 bean.
- optional ejb-link information, used to specify the
referenced enterprise bean
- optional elements to define injection of the named enterprise
bean into a component field or property
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
complexType "javaee:emptyType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| /> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
This type is used to designate an empty
element when used.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type is used to designate an empty
element when used.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:env-entry-type-valuesType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "java.lang.Boolean" | "java.lang.Byte" | "java.lang.Character" | "java.lang.String" | "java.lang.Short" | "java.lang.Integer" | "java.lang.Long" | "java.lang.Float" | "java.lang.Double" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
The following are the legal values of env-entry-type-valuesType:
java.lang.Boolean
java.lang.Byte
java.lang.Character
java.lang.String
java.lang.Short
java.lang.Integer
java.lang.Long
java.lang.Float
java.lang.Double
Example:
<env-entry-type>java.lang.Boolean</env-entry-type>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:env-entry-type-valuesType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"java.lang.Boolean", "java.lang.Byte", "java.lang.Character", "java.lang.String", "java.lang.Short", "java.lang.Integer", "java.lang.Long", "java.lang.Float", "java.lang.Double" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
This type contains the fully-qualified Java type of the
environment entry value that is expected by the
application's code.
The following are the legal values of env-entry-type-valuesType:
java.lang.Boolean
java.lang.Byte
java.lang.Character
java.lang.String
java.lang.Short
java.lang.Integer
java.lang.Long
java.lang.Float
java.lang.Double
Example:
<env-entry-type>java.lang.Boolean</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="java.lang.Boolean"/>
<xsd:enumeration value="java.lang.Byte"/>
<xsd:enumeration value="java.lang.Character"/>
<xsd:enumeration value="java.lang.String"/>
<xsd:enumeration value="java.lang.Short"/>
<xsd:enumeration value="java.lang.Integer"/>
<xsd:enumeration value="java.lang.Long"/>
<xsd:enumeration value="java.lang.Float"/>
<xsd:enumeration value="java.lang.Double"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:env-entryType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (6):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The env-entryType is used to declare an application's
environment entry. The declaration consists of an optional
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
If a value is not specified and injection is requested,
no injection will occur and no entry of the specified name
will be created. This allows an initial value to be
specified in the source code without being incorrectly
changed when no override has been specified.
If a value is not specified and no injection is requested,
a value must be supplied during deployment.
This type is used by env-entry elements.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The env-entryType is used to declare an application's
environment entry. The declaration consists of an optional
description, the name of the environment entry, a type
(optional if the value is injected, otherwise required), and
an optional value.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
If a value is not specified and injection is requested,
no injection will occur and no entry of the specified name
will be created. This allows an initial value to be
specified in the source code without being incorrectly
changed when no override has been specified.
If a value is not specified and no injection is requested,
a value must be supplied during deployment.
This type is used by env-entry elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-name element contains the name of a
Deployment Component's environment entry. The name
is a JNDI name relative to the java:comp/env
context. The name must be unique within a
Deployment Component. The uniqueness
constraints must be defined within the declared
context.
Example:
<env-entry-name>minAmount</env-entry-name>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-type element contains the Java language
type of the environment entry. If an injection target
is specified for the environment entry, the type may
be omitted, or must match the type of the injection
target. If no injection target is specified, the type
is required.
Example:
<env-entry-type>java.lang.Integer</env-entry-type>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The env-entry-value designates the value of a
Deployment Component's environment entry. The value
must be a String that is valid for the
constructor of the specified type that takes a
single String parameter, or for java.lang.Character,
a single character.
Example:
<env-entry-value>100.00</env-entry-value>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:error-codeType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ xsd:positiveInteger } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The error-code contains an HTTP error code, ex: 404
Used in: error-page
Type Definition Detail
| Type Derivation Tree xsd:positiveInteger javaee:error-codeType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The error-code contains an HTTP error code, ex: 404
Used in: error-page
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="\d{3}"/>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:error-pageType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (3):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The error-pageType contains a mapping between an error code
or exception type to the path of a resource in the web
application.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
The exception-type contains a fully qualified class
name of a Java exception type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
<xsd:documentation>
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The exception-type contains a fully qualified class
name of a Java exception type.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The exception-type contains a fully qualified class
name of a Java exception type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The location element contains the location of the
resource in the web application relative to the root of
the web application. The value of the location must have
a leading `/'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:filter-mappingType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (4):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
Declaration of the filter mappings in this web
application is done by using filter-mappingType.
The container uses the filter-mapping
declarations to decide which filters to apply to a request,
and in what order. The container matches the request URI to
a Servlet in the normal way. To determine which filters to
apply it matches filter-mapping declarations either on
servlet-name, or on url-pattern for each filter-mapping
element, depending on which style is used. The order in
which filters are invoked is the order in which
filter-mapping declarations that match a request URI for a
servlet appear in the list of filter-mapping elements.The
filter-name value must be the value of the filter-name
sub-elements of one of the filter declarations in the
deployment descriptor.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Declaration of the filter mappings in this web
application is done by using filter-mappingType.
The container uses the filter-mapping
declarations to decide which filters to apply to a request,
and in what order. The container matches the request URI to
a Servlet in the normal way. To determine which filters to
apply it matches filter-mapping declarations either on
servlet-name, or on url-pattern for each filter-mapping
element, depending on which style is used. The order in
which filters are invoked is the order in which
filter-mapping declarations that match a request URI for a
servlet appear in the list of filter-mapping elements.The
filter-name value must be the value of the filter-name
sub-elements of one of the filter declarations in the
deployment descriptor.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice maxOccurs="unbounded" minOccurs="1">
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:filter-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The logical name of the filter is declare
by using filter-nameType. This name is used to map the
filter. Each filter name is unique within the web
application.
Used in: filter, filter-mapping
Type Definition Detail
| Type Derivation Tree xsd:token javaee:filter-nameType (extension) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The logical name of the filter is declare
by using filter-nameType. This name is used to map the
filter. Each filter name is unique within the web
application.
Used in: filter, filter-mapping
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:filterType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (6):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The filterType is used to declare a filter in the web
application. The filter is mapped to either a servlet or a
URL pattern in the filter-mapping element, using the
filter-name value to reference. Filters can access the
initialization parameters declared in the deployment
descriptor at runtime via the FilterConfig interface.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The filterType is used to declare a filter in the web
application. The filter is mapped to either a servlet or a
URL pattern in the filter-mapping element, using the
filter-name value to reference. Filters can access the
initialization parameters declared in the deployment
descriptor at runtime via the FilterConfig interface.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The fully qualified classname of the filter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The init-param element contains a name/value pair as
an initialization param of a servlet filter
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The fully qualified classname of the filter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The fully qualified classname of the filter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The init-param element contains a name/value pair as
an initialization param of a servlet filter
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The init-param element contains a name/value pair as
an initialization param of a servlet filter
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:form-login-configType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
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
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The form-login-configType specifies the login and error
pages that should be used in form based login. If form based
authentication is not used, these elements are ignored.
Used in: login-config
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The form-error-page element defines the location in
the web app where the error page that is displayed
when login is not successful can be found.
The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The form-login-page element defines the location in the web
app where the page that can be used for login can be
found. The path begins with a leading / and is interpreted
relative to the root of the WAR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:fully-qualified-classType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (5):
-
All Direct / Indirect Based Elements (17):
-
Known Usage Locations
Annotation
The elements that use this type designate the name of a
Java class or interface. The name is in the form of a
"binary name", as defined in the JLS. This is the form
of name used in Class.forName(). Tools that need the
canonical name (the name used in source code) will need
to convert this binary name to the canonical name.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:fully-qualified-classType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The elements that use this type designate the name of a
Java class or interface. The name is in the form of a
"binary name", as defined in the JLS. This is the form
of name used in Class.forName(). Tools that need the
canonical name (the name used in source code) will need
to convert this binary name to the canonical name.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:generic-booleanType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
never |
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "true" | "false" | "yes" | "no" } |
|
| </...> |
Annotation
This type defines four different values which can designate
boolean values. This includes values yes and no which are
not designated by xsd:boolean
Type Definition Detail
| Type Derivation Tree xsd:token javaee:generic-booleanType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"true", "false", "yes", "no" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type defines four different values which can designate
boolean values. This includes values yes and no which are
not designated by xsd:boolean
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="true"/>
<xsd:enumeration value="false"/>
<xsd:enumeration value="yes"/>
<xsd:enumeration value="no"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:homeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The homeType defines the fully-qualified name of
an enterprise bean's home interface.
Example:
<home>com.aardvark.payroll.PayrollHome</home>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:homeType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The homeType defines the fully-qualified name of
an enterprise bean's home interface.
Example:
<home>com.aardvark.payroll.PayrollHome</home>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:iconType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 2 attributes and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
xml:lang |
= |
(xs:language | "") |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The icon type contains small-icon and large-icon elements
that specify the file names for small and large GIF, JPEG,
or PNG icon images used to represent the parent element in a
GUI tool.
The xml:lang attribute defines the language that the
icon file names are provided in. Its value is "en" (English)
by default.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The icon type contains small-icon and large-icon elements
that specify the file names for small and large GIF, JPEG,
or PNG icon images used to represent the parent element in a
GUI tool.
The xml:lang attribute defines the language that the
icon file names are provided in. Its value is "en" (English)
by default.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
Content Element Detail
-
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The large-icon element contains the name of a file
containing a large
(32 x 32) icon image. The file name is a relative
path within the Deployment Component's Deployment
File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<large-icon>employee-service-icon32x32.jpg</large-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The small-icon element contains the name of a file
containing a small (16 x 16) icon image. The file
name is a relative path within the Deployment
Component's Deployment File.
The image may be in the GIF, JPEG, or PNG format.
The icon can be used by tools.
Example:
<small-icon>employee-service-icon16x16.jpg</small-icon>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:injection-targetType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
| XML Representation Summary |
| <...> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
An injection target specifies a class and a name within
that class into which a resource should be injected.
The injection target class specifies the fully qualified
class name that is the target of the injection. The
Java EE specifications describe which classes can be an
injection target.
The injection target name specifies the target within
the specified class. The target is first looked for as a
JavaBeans property name. If not found, the target is
looked for as a field name.
The specified resource will be injected into the target
during initialization of the class by either calling the
set method for the target property or by setting a value
into the named field.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
An injection target specifies a class and a name within
that class into which a resource should be injected.
The injection target class specifies the fully qualified
class name that is the target of the injection. The
Java EE specifications describe which classes can be an
injection target.
The injection target name specifies the target within
the specified class. The target is first looked for as a
JavaBeans property name. If not found, the target is
looked for as a field name.
The specified resource will be injected into the target
during initialization of the class by either calling the
set method for the target property or by setting a value
into the named field.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:java-identifierType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
The java-identifierType defines a Java identifier.
The users of this type should further verify that
the content does not contain Java reserved keywords.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:java-identifierType (restriction) |
Derivation: |
|
Facets: |
pattern: |
($|_|\p{L})(\p{L}|\p{Nd}|_|$)* |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The java-identifierType defines a Java identifier.
The users of this type should further verify that
the content does not contain Java reserved keywords.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:java-typeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
never |
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Annotation
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.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:java-typeType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This is a generic type that designates a Java primitive
type or a fully qualified name of a Java interface/type,
or an array of such types.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="[^\p{Z}]*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:jndi-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (8):
-
Known Usage Locations
Annotation
The jndi-nameType type designates a JNDI name in the
Deployment Component's environment and is relative to the
java:comp/env context. A JNDI name must be unique within the
Deployment Component.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:jndi-nameType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The jndi-nameType type designates a JNDI name in the
Deployment Component's environment and is relative to the
java:comp/env context. A JNDI name must be unique within the
Deployment Component.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:jsp-configType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:jsp-fileType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The jsp-file element contains the full path to a JSP file
within the web application beginning with a `/'.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:jsp-fileType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:jsp-property-groupType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
javaee:description*, javaee:display-name*, javaee:icon*, javaee:url-pattern+, javaee:el-ignored?, javaee:page-encoding?, javaee:scripting-invalid?, javaee:is-xml?, javaee:include-prelude*, javaee:include-coda*, javaee:deferred-syntax-allowed-as-literal?, javaee:trim-directive-whitespaces? |
|
| </...> |
Content Elements (12):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The jsp-property-groupType is used to group a number of
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.
- Indicate that a resource is a JSP document (XML).
- Prelude and Coda automatic includes.
- Control whether the character sequence #{ is allowed
when used as a String literal.
- Control whether template text containing only
whitespaces must be removed from the response output.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The jsp-property-groupType is used to group a number of
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.
- Indicate that a resource is a JSP document (XML).
- Prelude and Coda automatic includes.
- Control whether the character sequence #{ is allowed
when used as a String literal.
- Control whether template text containing only
whitespaces must be removed from the response output.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
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>
<xsd:annotation>
<xsd:documentation>
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
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>
<xsd:annotation>
<xsd:documentation>
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
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>
<xsd:annotation>
<xsd:documentation>
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
<xsd:annotation>
<xsd:documentation>
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
<xsd:annotation>
<xsd:documentation>
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Indicates that template text containing only whitespaces
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The character sequence #{ is reserved for EL expressions.
Consequently, a translation error occurs if the #{
character sequence is used as a String literal, unless
this element is enabled (true). Disabled (false) by
default.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
EL evaluation is enabled for Web Applications using
a Servlet 2.4 or greater web.xml, and disabled
otherwise.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Can be used to easily set the isELIgnored
property of a group of JSP pages. By default, the
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>
-
XML Source (see within schema source)
-
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the end of each
JSP page in this jsp-property-group.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The include-coda element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
-
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
the given path will be automatically included (as
in an include directive) at the beginning of each
JSP page in this jsp-property-group.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The include-prelude element is a context-relative
path that must correspond to an element in the
Web Application. When the element is present,
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>
-
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
If false, the resources are assumed to not
be JSP documents, unless there is another
property group that indicates otherwise.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
If true, denotes that the group of resources
that match the URL pattern are JSP documents,
and thus must be interpreted as XML documents.
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>
-
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
in a JSP configuration element matching the document.
It is legal to name the same encoding through
mulitple mechanisms.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The valid values of page-encoding are those of the
pageEncoding page directive. It is a
translation-time error to name different encodings
in the pageEncoding attribute of the page directive
of a JSP page and in a JSP configuration element
matching the page. It is also a translation-time
error to name different encodings in the prolog
or text declaration of a document in XML syntax and
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>
-
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Can be used to easily disable scripting in a
group of JSP pages. By default, scripting is
enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Indicates that template text containing only whitespaces
must be removed from the response output. It has no
effect on JSP documents (XML syntax). Disabled (false)
by default.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Indicates that template text containing only whitespaces
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>
-
XML Source (see within schema source)
complexType "javaee:lifecycle-callbackType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
| XML Representation Summary |
| <...> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
The lifecycle-callback type specifies a method on a
class to be called when a lifecycle event occurs.
Note that each class may have only one lifecycle callback
method for any given event and that the method may not
be overloaded.
If the lifefycle-callback-class element is missing then
the class defining the callback is assumed to be the
component class in scope at the place in the descriptor
in which the callback definition appears.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The lifecycle-callback type specifies a method on a
class to be called when a lifecycle event occurs.
Note that each class may have only one lifecycle callback
method for any given event and that the method may not
be overloaded.
If the lifefycle-callback-class element is missing then
the class defining the callback is assumed to be the
component class in scope at the place in the descriptor
in which the callback definition appears.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:listenerType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (4):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The listenerType indicates the deployment properties for a web
application listener bean.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The listenerType indicates the deployment properties for a web
application listener bean.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The listener-class element declares a class in the
application must be registered as a web
application listener bean. The value is the fully
qualified classname of the listener class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:local-homeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:local-homeType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The local-homeType defines the fully-qualified
name of an enterprise bean's local home interface.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:locale-encoding-mapping-listType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The locale-encoding-mapping-list contains one or more
locale-encoding-mapping(s).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
complexType "javaee:locale-encoding-mappingType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The locale-encoding-mapping contains locale name and
encoding name. The locale name must be either "Language-code",
such as "ja", defined by ISO-639 or "Language-code_Country-code",
such as "ja_JP". "Country code" is defined by ISO-3166.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The locale-encoding-mapping contains locale name and
encoding name. The locale name must be either "Language-code",
such as "ja", defined by ISO-639 or "Language-code_Country-code",
such as "ja_JP". "Country code" is defined by ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:localType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The localType defines the fully-qualified name of an
enterprise bean's local interface.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:localType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The localType defines the fully-qualified name of an
enterprise bean's local interface.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:login-configType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (3):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The login-configType is used to configure the authentication
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The login-configType is used to configure the authentication
method that should be used, the realm name that should be
used for this application, and the attributes that are
needed by the form login mechanism.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The realm name element specifies the realm name to
use in HTTP Basic authorization.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The realm name element specifies the realm name to
use in HTTP Basic authorization.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The realm name element specifies the realm name to
use in HTTP Basic authorization.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:message-destination-linkType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
The Assembler sets the value to reflect the flow of messages
between producers and consumers in the application.
The value must be the message-destination-name of a message
destination in the same Deployment File or in another
Deployment File in the same Java EE application unit.
Alternatively, the value may be composed of a path name
specifying a Deployment File containing the referenced
message destination with the message-destination-name of the
destination appended and separated from the path name by
"#". The path name is relative to the Deployment File
containing Deployment Component that is referencing the
message destination. This allows multiple message
destinations with the same name to be uniquely identified.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:message-destination-linkType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-linkType is used to link a message
destination reference or message-driven bean to a message
destination.
The Assembler sets the value to reflect the flow of messages
between producers and consumers in the application.
The value must be the message-destination-name of a message
destination in the same Deployment File or in another
Deployment File in the same Java EE application unit.
Alternatively, the value may be composed of a path name
specifying a Deployment File containing the referenced
message destination with the message-destination-name of the
destination appended and separated from the path name by
"#". The path name is relative to the Deployment File
containing Deployment Component that is referencing the
message destination. This allows multiple message
destinations with the same name to be uniquely identified.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:message-destination-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (7):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The message-destination-ref element contains a declaration
of Deployment Component's reference to a message destination
associated with a resource in Deployment Component's
environment. It consists of:
- an optional description
- the message destination reference name
- an optional message destination type
- an optional specification as to whether
the destination is used for
consuming or producing messages, or both.
if not specified, "both" is assumed.
- an optional link to the message destination
- optional injection targets
The message destination type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Examples:
<message-destination-ref>
<message-destination-ref-name>jms/StockQueue
</message-destination-ref-name>
<message-destination-type>javax.jms.Queue
</message-destination-type>
<message-destination-usage>Consumes
</message-destination-usage>
<message-destination-link>CorporateStocks
</message-destination-link>
</message-destination-ref>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destination-ref element contains a declaration
of Deployment Component's reference to a message destination
associated with a resource in Deployment Component's
environment. It consists of:
- an optional description
- the message destination reference name
- an optional message destination type
- an optional specification as to whether
the destination is used for
consuming or producing messages, or both.
if not specified, "both" is assumed.
- an optional link to the message destination
- optional injection targets
The message destination type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Examples:
<message-destination-ref>
<message-destination-ref-name>jms/StockQueue
</message-destination-ref-name>
<message-destination-type>javax.jms.Queue
</message-destination-type>
<message-destination-usage>Consumes
</message-destination-usage>
<message-destination-link>CorporateStocks
</message-destination-link>
</message-destination-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-ref-name element specifies
the name of a message destination reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context and must be
unique within an ejb-jar (for enterprise beans) or a
Deployment File (for others).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:message-destination-typeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The message-destination-typeType specifies the type of
the destination. The type is specified by the Java interface
expected to be implemented by the destination.
Example:
<message-destination-type>javax.jms.Queue
</message-destination-type>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:message-destination-typeType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destination-typeType specifies the type of
the destination. The type is specified by the Java interface
expected to be implemented by the destination.
Example:
<message-destination-type>javax.jms.Queue
</message-destination-type>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:message-destination-usageType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Consumes" | "Produces" | "ConsumesProduces" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The message-destination-usageType specifies the use of the
message destination indicated by the reference. The value
indicates whether messages are consumed from the message
destination, produced for the destination, or both. The
Assembler makes use of this information in linking producers
of a destination with its consumers.
The value of the message-destination-usage element must be
one of the following:
Consumes
Produces
ConsumesProduces
Type Definition Detail
| Type Derivation Tree xsd:token javaee:message-destination-usageType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"Consumes", "Produces", "ConsumesProduces" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-usageType specifies the use of the
message destination indicated by the reference. The value
indicates whether messages are consumed from the message
destination, produced for the destination, or both. The
Assembler makes use of this information in linking producers
of a destination with its consumers.
The value of the message-destination-usage element must be
one of the following:
Consumes
Produces
ConsumesProduces
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Consumes"/>
<xsd:enumeration value="Produces"/>
<xsd:enumeration value="ConsumesProduces"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:message-destinationType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (5):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The message-destinationType specifies a message
destination. The logical destination described by this
element is mapped to a physical destination by the Deployer.
The message destination element contains:
- an optional description
- an optional display-name
- an optional icon
- a message destination name which must be unique
among message destination names within the same
Deployment File.
- an optional mapped name
Example:
<message-destination>
<message-destination-name>CorporateStocks
</message-destination-name>
</message-destination>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The message-destinationType specifies a message
destination. The logical destination described by this
element is mapped to a physical destination by the Deployer.
The message destination element contains:
- an optional description
- an optional display-name
- an optional icon
- a message destination name which must be unique
among message destination names within the same
Deployment File.
- an optional mapped name
Example:
<message-destination>
<message-destination-name>CorporateStocks
</message-destination-name>
</message-destination>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this message destination
should be mapped to. Each message-destination-ref
element that references this message destination will
define a name in the namespace of the referencing
component. (It's a name in the JNDI java:comp/env
namespace.) Many application servers provide a way to
map these local names to names of resources known to the
application server. This mapped name is often a global
JNDI name, but may be a name of any form. Each of the
local names should be mapped to this same global name.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:mime-mappingType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The mime-mappingType defines a mapping between an extension
and a mime type.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The mime-mappingType defines a mapping between an extension
and a mime type.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The extension element contains a string describing an
extension. example: "txt"
</xsd:documentation>
</xsd:annotation>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:mime-typeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The mime-typeType is used to indicate a defined mime type.
Example:
"text/plain"
Used in: mime-mapping
Type Definition Detail
| Type Derivation Tree xsd:token javaee:mime-typeType (restriction) |
Derivation: |
|
Facets: |
pattern: |
[^\p{Cc}^\s]+/[^\p{Cc}^\s]+ |
|
XML Source (see within schema source) <xsd:annotation>
<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>
<xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:nonEmptyStringType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (2):
-
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- In derivations of other global types (2):
Annotation
This type defines a string which contains at least one
character.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:nonEmptyStringType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type defines a string which contains at least one
character.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:minLength value="1"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:param-valueType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (3):
-
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
This type is a general type that can be used to declare
parameter/value lists.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type is a general type that can be used to declare
parameter/value lists.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The param-name element contains the name of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The param-value element contains the value of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The param-name element contains the name of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-name element contains the name of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The param-value element contains the value of a
parameter.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The param-value element contains the value of a
parameter.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:pathType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (7):
-
Known Usage Locations
Annotation
The elements that use this type designate either a relative
path or an absolute path starting with a "/".
In elements that specify a pathname to a file within the
same Deployment File, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the Deployment File's namespace. Absolute filenames (i.e.,
those starting with "/") also specify names in the root of
the Deployment File's namespace. In general, relative names
are preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:pathType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The elements that use this type designate either a relative
path or an absolute path starting with a "/".
In elements that specify a pathname to a file within the
same Deployment File, relative filenames (i.e., those not
starting with "/") are considered relative to the root of
the Deployment File's namespace. Absolute filenames (i.e.,
those starting with "/") also specify names in the root of
the Deployment File's namespace. In general, relative names
are preferred. The exception is .war files where absolute
names are preferred for consistency with the Servlet API.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:persistence-context-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (7):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The persistence-context-ref element contains a declaration
of Deployment Component's reference to a persistence context
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence context reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- an optional specification as to whether
the persistence context type is Transaction or
Extended. If not specified, Transaction is assumed.
- an optional list of persistence properties
- optional injection targets
Examples:
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
</persistence-context-ref>
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
<persistence-context-type>Extended</persistence-context-type>
</persistence-context-ref>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The persistence-context-ref element contains a declaration
of Deployment Component's reference to a persistence context
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence context reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- an optional specification as to whether
the persistence context type is Transaction or
Extended. If not specified, Transaction is assumed.
- an optional list of persistence properties
- optional injection targets
Examples:
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
</persistence-context-ref>
<persistence-context-ref>
<persistence-context-ref-name>myPersistenceContext
</persistence-context-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
<persistence-context-type>Extended</persistence-context-type>
</persistence-context-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The persistence-context-ref-name element specifies
the name of a persistence context reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Used to specify properties for the container or persistence
provider. Vendor-specific properties may be included in
the set of properties. Properties that are not recognized
by a vendor must be ignored. Entries that make use of the
namespace javax.persistence and its subnamespaces must not
be used for vendor-specific properties. The namespace
javax.persistence is reserved for use by the specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:persistence-context-typeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Transaction" | "Extended" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The persistence-context-typeType specifies the transactional
nature of a persistence context reference.
The value of the persistence-context-type element must be
one of the following:
Transaction
Extended
Type Definition Detail
| Type Derivation Tree xsd:token javaee:persistence-context-typeType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"Transaction", "Extended" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The persistence-context-typeType specifies the transactional
nature of a persistence context reference.
The value of the persistence-context-type element must be
one of the following:
Transaction
Extended
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Transaction"/>
<xsd:enumeration value="Extended"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:persistence-unit-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (5):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The persistence-unit-ref element contains a declaration
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence unit reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- optional injection targets
Examples:
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
</persistence-unit-ref>
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
</persistence-unit-ref>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The persistence-unit-ref element contains a declaration
of Deployment Component's reference to a persistence unit
associated within a Deployment Component's
environment. It consists of:
- an optional description
- the persistence unit reference name
- an optional persistence unit name. If not specified,
the default persistence unit is assumed.
- optional injection targets
Examples:
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
</persistence-unit-ref>
<persistence-unit-ref>
<persistence-unit-ref-name>myPersistenceUnit
</persistence-unit-ref-name>
<persistence-unit-name>PersistenceUnit1
</persistence-unit-name>
</persistence-unit-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The Application Assembler(or BeanProvider) may use the
following syntax to avoid the need to rename persistence
units to have unique names within a Java EE application.
The Application Assembler specifies the pathname of the
root of the persistence.xml file for the referenced
persistence unit and appends the name of the persistence
unit separated from the pathname by #. The pathname is
relative to the referencing application component jar file.
In this manner, multiple persistence units with the same
persistence unit name may be uniquely identified when the
Application Assembler cannot change persistence unit names.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The persistence-unit-ref-name element specifies
the name of a persistence unit reference; its
value is the environment entry name used in
Deployment Component code. The name is a JNDI name
relative to the java:comp/env context.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:port-component-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (3):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-component-link element links a port-component-ref
to a specific port-component required to be made available
by a service reference.
The value of a port-component-link must be the
port-component-name of a port-component in the same module
or another module in the same application unit. The syntax
for specification follows the syntax defined for ejb-link
in the EJB 2.0 specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Used to enable or disable SOAP MTOM/XOP mechanism on the client
side for a port-component.
Not to be specified for JAX-RPC runtime
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-component-link element links a port-component-ref
to a specific port-component required to be made available
by a service reference.
The value of a port-component-link must be the
port-component-name of a port-component in the same module
or another module in the same application unit. The syntax
for specification follows the syntax defined for ejb-link
in the EJB 2.0 specification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-endpoint-interface element defines a fully qualified
Java class that represents the Service Endpoint Interface of a
WSDL port.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:propertyType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
Specifies a name/value pair.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Specifies a name/value pair.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:element>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source) </xsd:element>
-
XML Source (see within schema source) </xsd:element>
complexType "javaee:remoteType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
Example:
<remote>com.wombat.empl.EmployeeService</remote>
Type Definition Detail
| Type Derivation Tree xsd:token javaee:remoteType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The remote element contains the fully-qualified name
of the enterprise bean's remote interface.
Example:
<remote>com.wombat.empl.EmployeeService</remote>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:res-authType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Application" | "Container" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The res-authType specifies whether the Deployment Component
code signs on programmatically to the resource manager, or
whether the Container will sign on to the resource manager
on behalf of the Deployment Component. In the latter case,
the Container uses information that is supplied by the
Deployer.
The value must be one of the two following:
Application
Container
Type Definition Detail
| Type Derivation Tree xsd:token javaee:res-authType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"Application", "Container" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-authType specifies whether the Deployment Component
code signs on programmatically to the resource manager, or
whether the Container will sign on to the resource manager
on behalf of the Deployment Component. In the latter case,
the Container uses information that is supplied by the
Deployer.
The value must be one of the two following:
Application
Container
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Application"/>
<xsd:enumeration value="Container"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:res-sharing-scopeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "Shareable" | "Unshareable" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The res-sharing-scope type specifies whether connections
obtained through the given resource manager connection
factory reference can be shared. The value, if specified,
must be one of the two following:
Shareable
Unshareable
The default value is Shareable.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:res-sharing-scopeType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"Shareable", "Unshareable" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-sharing-scope type specifies whether connections
obtained through the given resource manager connection
factory reference can be shared. The value, if specified,
must be one of the two following:
Shareable
Unshareable
The default value is Shareable.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="Shareable"/>
<xsd:enumeration value="Unshareable"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:resource-env-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (5):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The resource-env-refType is used to define
resource-env-type elements. It contains a declaration of a
Deployment Component's reference to an administered object
associated with a resource in the Deployment Component's
environment. It consists of an optional description, the
resource environment reference name, and an optional
indication of the resource environment reference type
expected by the Deployment Component code.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The resource environment type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-env-ref>
<resource-env-ref-name>jms/StockQueue
</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue
</resource-env-ref-type>
</resource-env-ref>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The resource-env-refType is used to define
resource-env-type elements. It contains a declaration of a
Deployment Component's reference to an administered object
associated with a resource in the Deployment Component's
environment. It consists of an optional description, the
resource environment reference name, and an optional
indication of the resource environment reference type
expected by the Deployment Component code.
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The resource environment type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-env-ref>
<resource-env-ref-name>jms/StockQueue
</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue
</resource-env-ref-type>
</resource-env-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The resource-env-ref-name element specifies the name
of a resource environment reference; its value is
the environment entry name used in
the Deployment Component code. The name is a JNDI
name relative to the java:comp/env context and must
be unique within a Deployment Component.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The resource-env-ref-type element specifies the type
of a resource environment reference. It is the
fully qualified name of a Java language class or
interface.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:resource-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 5 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (7):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The resource-refType contains a declaration of a
Deployment Component's reference to an external resource. It
consists of an optional description, the resource manager
connection factory reference name, an optional indication of
the resource manager connection factory type expected by the
Deployment Component code, an optional type of authentication
(Application or Container), and an optional specification of
the shareability of connections obtained from the resource
(Shareable or Unshareable).
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The connection factory type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-ref>
<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The resource-refType contains a declaration of a
Deployment Component's reference to an external resource. It
consists of an optional description, the resource manager
connection factory reference name, an optional indication of
the resource manager connection factory type expected by the
Deployment Component code, an optional type of authentication
(Application or Container), and an optional specification of
the shareability of connections obtained from the resource
(Shareable or Unshareable).
It also includes optional elements to define injection of
the named resource into fields or JavaBeans properties.
The connection factory type must be supplied unless an
injection target is specified, in which case the type
of the target is used. If both are specified, the type
must be assignment compatible with the type of the injection
target.
Example:
<resource-ref>
<res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference.
The name is a JNDI name relative to the
java:comp/env context.
The name must be unique within a Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-ref-name element specifies the name of a
resource manager connection factory reference.
The name is a JNDI name relative to the
java:comp/env context.
The name must be unique within a Deployment File.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The res-type element specifies the type of the data
source. The type is specified by the fully qualified
Java language class or interface
expected to be implemented by the data source.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:role-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
The role-nameType designates the name of a security role.
The name must conform to the lexical rules for a token.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:role-nameType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The role-nameType designates the name of a security role.
The name must conform to the lexical rules for a token.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:run-asType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The run-asType specifies the run-as identity to be
used for the execution of a component. It contains an
optional description, and the name of a security role.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The run-asType specifies the run-as identity to be
used for the execution of a component. It contains an
optional description, and the name of a security role.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:security-constraintType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (4):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The security-constraintType is used to associate
security constraints with one or more web resource
collections
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:security-role-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 3 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (3):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The security-role-refType contains the declaration of a
security role reference in a component's or a
Deployment Component's code. The declaration consists of an
optional description, the security role name used in the
code, and an optional link to a security role. If the
security role is not specified, the Deployer must choose an
appropriate security role.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The security-role-refType contains the declaration of a
security role reference in a component's or a
Deployment Component's code. The declaration consists of an
optional description, the security role name used in the
code, and an optional link to a security role. If the
security role is not specified, the Deployer must choose an
appropriate security role.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The role-link element is a reference to a defined
security role. The role-link element must contain
the name of one of the security roles defined in the
security-role elements.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The value of the role-name element must be the String used
as the parameter to the
EJBContext.isCallerInRole(String roleName) method or the
HttpServletRequest.isUserInRole(String role) method.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:security-roleType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The security-roleType contains the definition of a security
role. The definition consists of an optional description of
the security role, and the security role name.
Example:
<security-role>
<description>
This role includes all employees who are authorized
to access the employee service application.
</description>
<role-name>employee</role-name>
</security-role>
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
The security-roleType contains the definition of a security
role. The definition consists of an optional description of
the security role, and the security role name.
Example:
<security-role>
<description>
This role includes all employees who are authorized
to access the employee service application.
</description>
<role-name>employee</role-name>
</security-role>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:service-ref_handler-chainsType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The handler-chains element defines the handlerchains associated with this
service or service endpoint.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The handler-chains element defines the handlerchains associated with this
service or service endpoint.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
complexType "javaee:service-ref_handler-chainType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (4):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
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
choices are specified with the handler-chain element then the
handlers specified in the handler-chain will be applied on
everything.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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
choices are specified with the handler-chain element then the
handlers specified in the handler-chain will be applied on
everything.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice maxOccurs="1" minOccurs="0">
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:service-ref_handlerType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 6 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (9):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
Declares the handler for a port-component. Handlers can access the
init-param name/value pairs using the HandlerInfo interface. If
port-name is not specified, the handler is assumed to be associated
with all ports of the service.
Used in: service-ref
XML Source (see within schema source) <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.
Used in: service-ref
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Defines a fully qualified class name for the handler
implementation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Defines the QName of a SOAP header that will be processed
by the handler.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-name element defines the WSDL port-name that a
handler should be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Defines a fully qualified class name for the handler
implementation.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines a fully qualified class name for the handler
implementation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Defines the name of the handler. The name must be unique
within the module.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The port-name element defines the WSDL port-name that a
handler should be associated with.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-name element defines the WSDL port-name that a
handler should be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Defines the QName of a SOAP header that will be processed
by the handler.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the QName of a SOAP header that will be processed
by the handler.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The soap-role element contains a SOAP actor definition that
the Handler will play as a role.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:service-refType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 9 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
javaee:description*, javaee:display-name*, javaee:icon*, javaee:service-ref-name, javaee:service-interface, javaee:service-ref-type?, javaee:wsdl-file?, javaee:jaxrpc-mapping-file?, javaee:service-qname?, javaee:port-component-ref*, (javaee:handler* | javaee:handler-chains?), javaee:mapped-name?, javaee:injection-target* |
|
| </...> |
Content Elements (14):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The service-ref element declares a reference to a Web
service. It contains optional description, display name and
icons, a declaration of the required Service interface,
an optional WSDL document location, an optional set
of JAX-RPC mappings, an optional QName for the service element,
an optional set of Service Endpoint Interfaces to be resolved
by the container to a WSDL port, and an optional set of handlers.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-ref element declares a reference to a Web
service. It contains optional description, display name and
icons, a declaration of the required Service interface,
an optional WSDL document location, an optional set
of JAX-RPC mappings, an optional QName for the service element,
an optional set of Service Endpoint Interfaces to be resolved
by the container to a WSDL port, and an optional set of handlers.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The service-qname element declares the specific WSDL service
element that is being refered to. It is not specified if no
wsdl-file is declared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Declares the handler for a port-component. Handlers can
access the init-param name/value pairs using the
HandlerInfo interface. If port-name is not specified, the
handler is assumed to be associated with all ports of the
service.
To be used with JAX-RPC based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
To be used with JAX-WS based runtime only.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
To be used with JAX-WS based runtime only.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The jaxrpc-mapping-file element contains the name of a file that
describes the JAX-RPC mapping between the Java interaces used by
the application and the WSDL description in the wsdl-file. The
file name is a relative path within the module file.
This is not required when JAX-WS based runtime is used.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The port-component-ref element declares a client dependency
on the container for resolving a Service Endpoint Interface
to a WSDL port. It optionally associates the Service Endpoint
Interface with a particular port-component. This is only used
by the container for a Service.getPort(Class) method call.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-interface element declares the fully qualified class
name of the JAX-RPC Service interface the client depends on.
In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
generated Service Interface class may also be specified.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
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.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-qname element declares the specific WSDL service
element that is being refered to. It is not specified if no
wsdl-file is declared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-ref-name element declares logical name that the
components in the module use to look up the Web service. It
is recommended that all service reference names start with
"service/".
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The service-ref-type element declares the type of the service-ref
element that is injected or returned when a JNDI lookup is done.
This must be either a fully qualified name of Service class or
the fully qualified name of service endpoint interface class.
This is only used with JAX-WS runtime where the corresponding
@WebServiceRef annotation can be used to denote both a Service
or a Port.
If this is not specified, then the type of service-ref element
that is injected or returned when a JNDI lookup is done is
always a Service interface/class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The wsdl-file element contains the URI location of a WSDL
file. The location is relative to the root of the module.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:servlet-mappingType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The servlet-mappingType defines a mapping between a
servlet and a url pattern.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:servlet-nameType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The servlet-name element contains the canonical name of the
servlet. Each servlet name is unique within the web
application.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:servlet-nameType (extension) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:servletType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 7 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (10):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The servletType is used to declare a servlet.
It contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup
element is present, then the JSP should be precompiled and
loaded.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The servletType is used to declare a servlet.
It contains the declarative data of a
servlet. If a jsp-file is specified and the load-on-startup
element is present, then the JSP should be precompiled and
loaded.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:choice>
<xsd:annotation>
<xsd:documentation>
The servlet-class element contains the fully
qualified class name of the servlet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:annotation>
<xsd:documentation>
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The servlet-class element contains the fully
qualified class name of the servlet.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The servlet-class element contains the fully
qualified class name of the servlet.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
complexType "javaee:session-configType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The session-configType defines the session parameters
for this web application.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The session-configType defines the session parameters
for this web application.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
the default behaviour of sessions is never to time
out. If this element is not specified, the container
must set its default timeout period.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:string"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (22):
-
javaee:auth-methodType,
javaee:dispatcherType,
javaee:display-nameType,
javaee:ejb-linkType,
javaee:ejb-ref-typeType,
javaee:env-entry-type-valuesType,
javaee:fully-qualified-classType,
javaee:generic-booleanType,
javaee:java-identifierType,
javaee:java-typeType,
javaee:jndi-nameType,
javaee:message-destination-linkType,
javaee:message-destination-usageType,
javaee:mime-typeType,
javaee:nonEmptyStringType,
javaee:pathType,
javaee:persistence-context-typeType,
javaee:res-authType,
javaee:res-sharing-scopeType,
javaee:role-nameType,
javaee:transport-guaranteeType,
javaee:war-pathType
Known Indirect Subtypes (9):
-
All Direct / Indirect Based Elements (66):
-
Known Usage Locations
Annotation
This is a special string datatype that is defined by Java EE as
a base type for defining collapsed strings. When schemas
require trailing/leading space elimination as well as
collapsing the existing whitespace, this base type may be
used.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:string (extension) |
Derivation: |
extension of xsd:token |
XML Source (see within schema source) <xsd:complexType name="string"> <xsd:annotation>
<xsd:documentation>
This is a special string datatype that is defined by Java EE as
a base type for defining collapsed strings. When schemas
require trailing/leading space elimination as well as
collapsing the existing whitespace, this base type may be
used.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:token">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:taglibType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The taglibType defines the syntax for declaring in
the deployment descriptor that a tag library is
available to the application. This can be done
to override implicit map entries from TLD files and
from the container.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The taglibType defines the syntax for declaring in
the deployment descriptor that a tag library is
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>
<xsd:annotation>
<xsd:documentation>
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
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>
<xsd:annotation>
<xsd:documentation>
the taglib-location element contains the location
(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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
the taglib-location element contains the location
(as a resource relative to the root of the web
application) where to find the Tag Library
Description file for the tag library.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
the taglib-location element contains the location
(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>
-
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
absolute URI specification, or a relative URI.
There should be no entries in web.xml with the
same taglib-uri value.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
A taglib-uri element describes a URI identifying a
tag library used in the web application. The body
of the taglib-uri element may be either an
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>
complexType "javaee:transport-guaranteeType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ "NONE" | "INTEGRAL" | "CONFIDENTIAL" } |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The transport-guaranteeType specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL. NONE means that the application does not
require any transport guarantees. A value of INTEGRAL means
that the application requires that the data sent between the
client and server be sent in such a way that it can't be
changed in transit. CONFIDENTIAL means that the application
requires that the data be transmitted in a fashion that
prevents other entities from observing the contents of the
transmission. In most cases, the presence of the INTEGRAL or
CONFIDENTIAL flag will indicate that the use of SSL is
required.
Used in: user-data-constraint
Type Definition Detail
| Type Derivation Tree xsd:token javaee:transport-guaranteeType (restriction) |
Derivation: |
|
Facets: |
enumeration: |
"NONE", "INTEGRAL", "CONFIDENTIAL" |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The transport-guaranteeType specifies that the communication
between client and server should be NONE, INTEGRAL, or
CONFIDENTIAL. NONE means that the application does not
require any transport guarantees. A value of INTEGRAL means
that the application requires that the data sent between the
client and server be sent in such a way that it can't be
changed in transit. CONFIDENTIAL means that the application
requires that the data be transmitted in a fashion that
prevents other entities from observing the contents of the
transmission. In most cases, the presence of the INTEGRAL or
CONFIDENTIAL flag will indicate that the use of SSL is
required.
Used in: user-data-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:enumeration value="NONE"/>
<xsd:enumeration value="INTEGRAL"/>
<xsd:enumeration value="CONFIDENTIAL"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:true-falseType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (6):
-
Known Usage Locations
- As direct type of elements (6):
Annotation
This simple type designates a boolean with only two
permissible values
- true
- false
Type Definition Detail
| Type Derivation Tree xsd:boolean javaee:true-falseType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This simple type designates a boolean with only two
permissible values
- true
- false
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="(true|false)"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:url-patternType"
Namespace: |
|
Content: |
simple |
Defined: |
|
Used: |
|
| XML Representation Summary |
| <...> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The url-patternType contains the url pattern of the mapping.
It must follow the rules specified in Section 11.2 of the
Servlet API Specification. This pattern is assumed to be in
URL-decoded form and must not contain CR(#xD) or LF(#xA).
If it contains those characters, the container must inform
the developer with a descriptive error message.
The container must preserve all characters including whitespaces.
Type Definition Detail
| Type Derivation Tree xsd:string javaee:url-patternType (extension) |
Derivation: |
extension of xsd:string |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The url-patternType contains the url pattern of the mapping.
It must follow the rules specified in Section 11.2 of the
Servlet API Specification. This pattern is assumed to be in
URL-decoded form and must not contain CR(#xD) or LF(#xA).
If it contains those characters, the container must inform
the developer with a descriptive error message.
The container must preserve all characters including whitespaces.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string"/>
</xsd:simpleContent>
</xsd:complexType>
complexType "javaee:user-data-constraintType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 2 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (2):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The user-data-constraintType is used to indicate how
data communicated between the client and container should be
protected.
Used in: security-constraint
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:war-pathType"
Namespace: |
|
Content: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (3):
-
Known Usage Locations
- As direct type of elements (3):
Annotation
The elements that use this type designate a path starting
with a "/" and interpreted relative to the root of a WAR
file.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:war-pathType (restriction) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The elements that use this type designate a path starting
with a "/" and interpreted relative to the root of a WAR
file.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:pattern value="/.*"/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:web-appType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 3 attributes and 17 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
metadata-complete |
= |
xsd:boolean |
| |
version |
= |
"2.5" |
| |
> |
| |
Content: |
((javaee:description*, javaee:display-name*, javaee:icon*) | javaee:distributable | javaee:context-param | javaee:filter | javaee:filter-mapping | javaee:listener | javaee:servlet | javaee:servlet-mapping | javaee:session-config | javaee:mime-mapping | javaee:welcome-file-list | javaee:error-page | javaee:jsp-config | javaee:security-constraint | javaee:login-config | javaee:security-role | (javaee:env-entry*, javaee:ejb-ref*, javaee:ejb-local-ref*, javaee:service-ref*, javaee:resource-ref*, javaee:resource-env-ref*, javaee:message-destination-ref*, javaee:persistence-context-ref*, javaee:persistence-unit-ref*, javaee:post-construct*, javaee:pre-destroy*) | javaee:message-destination | javaee:locale-encoding-mapping-list)* |
|
| </...> |
Content Elements (31):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
XML Source (see within schema source) <xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
<xsd:attribute name="id" type="xsd:ID"/> <xsd:annotation>
<xsd:documentation>
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
metadata-complete
-
Type: |
xsd:boolean, predefined |
Use: |
optional |
Defined: |
|
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The metadata-complete attribute defines whether this
deployment descriptor and other related deployment
descriptors for this module (e.g., web service
descriptors) are complete, or whether the class
files available to this module and packaged with
this application should be examined for annotations
that specify deployment information.
If metadata-complete is set to "true", the deployment
tool must ignore any annotations that specify deployment
information, which might be present in the class files
of the application.
If metadata-complete is not specified or is set to
"false", the deployment tool must examine the class
files of the application for annotations, as
specified by the specifications.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
version
-
Type: |
|
Use: |
required |
Defined: |
|
XML Source (see within schema source)
Content Element Detail
-
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The context-param element contains the declaration
of a web application's servlet context
initialization parameters.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source) <xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
complexType "javaee:web-resource-collectionType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 4 elements |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (4):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The web-resource-collectionType is used to identify a subset
of the resources and HTTP methods on those resources within
a web application to which a security constraint applies. If
no HTTP methods are specified, then the security constraint
applies to all HTTP methods.
Used in: security-constraint
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The web-resource-collectionType is used to identify a subset
of the resources and HTTP methods on those resources within
a web application to which a security constraint applies. If
no HTTP methods are specified, then the security constraint
applies to all HTTP methods.
Used in: security-constraint
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
The web-resource-name contains the name of this web
resource collection.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
The web-resource-name contains the name of this web
resource collection.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The web-resource-name contains the name of this web
resource collection.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:welcome-file-listType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 1 attribute and 1 element |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Content Elements (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The welcome-file-list contains an ordered list of welcome
files elements.
Used in: web-app
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The welcome-file-list contains an ordered list of welcome
files elements.
Used in: web-app
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="welcome-file" type="xsd:string"> <xsd:annotation>
<xsd:documentation>
The welcome-file element contains file name to use
as a default welcome file, such as index.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID"/> </xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
Content Element Detail
-
Type: |
xsd:string, predefined, simple content |
Defined: |
|
The welcome-file element contains file name to use
as a default welcome file, such as index.html
XML Source (see within schema source) <xsd:element maxOccurs="unbounded" name="welcome-file" type="xsd:string"> <xsd:annotation>
<xsd:documentation>
The welcome-file element contains file name to use
as a default welcome file, such as index.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
complexType "javaee:xsdAnyURIType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
This type adds an "id" attribute to xsd:anyURI.
Type Definition Detail
| Type Derivation Tree xsd:anyURI javaee:xsdAnyURIType (extension) |
Derivation: |
extension of xsd:anyURI |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:anyURI.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:anyURI">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdBooleanType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (6):
-
Known Usage Locations
- In derivations of other global types (1):
Annotation
This type adds an "id" attribute to xsd:boolean.
Type Definition Detail
| Type Derivation Tree xsd:boolean javaee:xsdBooleanType (extension) |
Derivation: |
extension of xsd:boolean |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:boolean.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:boolean">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdIntegerType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
This type adds an "id" attribute to xsd:integer.
Type Definition Detail
| Type Derivation Tree xsd:integer javaee:xsdIntegerType (extension) |
Derivation: |
extension of xsd:integer |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:integer.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:integer">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdNMTOKENType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Annotation
This type adds an "id" attribute to xsd:NMTOKEN.
Type Definition Detail
| Type Derivation Tree xsd:NMTOKEN javaee:xsdNMTOKENType (extension) |
Derivation: |
extension of xsd:NMTOKEN |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:NMTOKEN.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:NMTOKEN">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdNonNegativeIntegerType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
never |
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ xsd:nonNegativeInteger } |
|
| </...> |
Annotation
This type adds an "id" attribute to xsd:nonNegativeInteger.
Type Definition Detail
| Type Derivation Tree xsd:nonNegativeInteger javaee:xsdNonNegativeIntegerType (extension) |
Derivation: |
extension of xsd:nonNegativeInteger |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:nonNegativeInteger.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:nonNegativeInteger">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdPositiveIntegerType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
Content: |
{ xsd:positiveInteger } |
|
| </...> |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- In derivations of other global types (1):
Annotation
This type adds an "id" attribute to xsd:positiveInteger.
Type Definition Detail
| Type Derivation Tree xsd:positiveInteger javaee:xsdPositiveIntegerType (extension) |
Derivation: |
extension of xsd:positiveInteger |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:positiveInteger.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:positiveInteger">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdQNameType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
This type adds an "id" attribute to xsd:QName.
Type Definition Detail
| Type Derivation Tree xsd:QName javaee:xsdQNameType (extension) |
Derivation: |
extension of xsd:QName |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:QName.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:QName">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
complexType "javaee:xsdStringType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 attribute |
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xsd:ID |
| |
> |
| |
|
| </...> |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (6):
-
Known Usage Locations
Annotation
This type adds an "id" attribute to xsd:string.
Type Definition Detail
| Type Derivation Tree xsd:string javaee:xsdStringType (extension) |
Derivation: |
extension of xsd:string |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type adds an "id" attribute to xsd:string.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="id" type="xsd:ID"/> </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
Attribute Detail
id
-
Type: |
xsd:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source) <xsd:attribute name="id" type="xsd:ID"/>
simpleType "javaee:dewey-versionType"
Namespace: |
|
Defined: |
|
Used: |
never |
| Simple Content Model |
| xsd:token |
Annotation
This type defines a dewey decimal that is used
to describe versions of documents.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:dewey-versionType (restriction) |
Derivation: |
restriction of xsd:token |
Facets: |
pattern: |
\.?[0-9]+(\.[0-9]+)* |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type defines a dewey decimal that is used
to describe versions of documents.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:encodingType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:string |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The encodingType defines IANA character sets.
Type Definition Detail
| Type Derivation Tree xsd:string javaee:encodingType (restriction) |
Derivation: |
restriction of xsd:string |
Facets: |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The encodingType defines IANA character sets.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[^\s]+"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:http-methodType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:token |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
A HTTP method type as defined in HTTP 1.1 section 2.2.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:http-methodType (restriction) |
Derivation: |
restriction of xsd:token |
Facets: |
pattern: |
[!-~-[\(\)<>@,;:"/\[\]?=\{\}\\\p{Z}]]+ |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
A HTTP method type as defined in HTTP 1.1 section 2.2.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="[!-~-[\(\)<>@,;:"/\[\]?=\{\}\\\p{Z}]]+"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:load-on-startupType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| "" | xsd:integer |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Type Definition Detail
| Type Derivation Tree javaee:load-on-startupType |
Member Types
XML Source (see within schema source) </xsd:simpleType>
simpleType "javaee:localeType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:string |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
The localeType defines valid locale defined by ISO-639-1
and ISO-3166.
Type Definition Detail
| Type Derivation Tree xsd:string javaee:localeType (restriction) |
Derivation: |
restriction of xsd:string |
Facets: |
pattern: |
[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})? |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
The localeType defines valid locale defined by ISO-639-1
and ISO-3166.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:null-charType"
Namespace: |
|
Defined: |
|
Used: |
|
Known Usage Locations
- In derivations of other global types (1):
Type Definition Detail
| Type Derivation Tree xsd:string javaee:null-charType (restriction) |
Derivation: |
restriction of xsd:string |
Facets: |
|
XML Source (see within schema source) <xsd:restriction base="xsd:string">
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:service-ref_protocol-bindingListType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| list of (xsd:anyURI | xsd:token) |
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- As direct type of elements (1):
Annotation
Defines the type used for specifying a list of
protocol-bindingType(s). For e.g.
##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
Type Definition Detail
| Type Derivation Tree javaee:service-ref_protocol-bindingListType (list) |
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
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:simpleType>
simpleType "javaee:service-ref_protocol-bindingType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:anyURI | xsd:token |
Known Direct Subtypes (1):
-
All Direct / Indirect Based Elements (1):
-
Known Usage Locations
- In derivations of other global types (1):
Annotation
Defines the type used for specifying the URI for the
protocol binding used by the port-component. For
portability one could use one of the following tokens that
alias the standard binding types:
##SOAP11_HTTP
##SOAP11_HTTP_MTOM
##SOAP12_HTTP
##SOAP12_HTTP_MTOM
##XML_HTTP
Other specifications could define tokens that start with ##
to alias new standard binding URIs that are introduced.
Type Definition Detail
| Type Derivation Tree javaee:service-ref_protocol-bindingType |
Member Types
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the type used for specifying the URI for the
protocol binding used by the port-component. For
portability one could use one of the following tokens that
alias the standard binding types:
##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:simpleType>
simpleType "javaee:service-ref_protocol-URIAliasType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:token |
Known Usage Locations
- In derivations of other global types (1):
Annotation
Defines the type that is used for specifying tokens that
start with ## which are used to alias existing standard
protocol bindings and support aliases for new standard
binding URIs that are introduced in future specifications.
The following tokens alias the standard protocol binding
URIs:
##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
##SOAP11_HTTP_MTOM =
"http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
##SOAP12_HTTP_MTOM =
"http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
Type Definition Detail
| Type Derivation Tree xsd:token javaee:service-ref_protocol-URIAliasType (restriction) |
Derivation: |
restriction of xsd:token |
Facets: |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
Defines the type that is used for specifying tokens that
start with ## which are used to alias existing standard
protocol bindings and support aliases for new standard
binding URIs that are introduced in future specifications.
The following tokens alias the standard protocol binding
URIs:
##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
##SOAP11_HTTP_MTOM =
"http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
##SOAP12_HTTP_MTOM =
"http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="##.+"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:service-ref_qname-pattern"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| xsd:token |
All Direct / Indirect Based Elements (2):
-
Known Usage Locations
- As direct type of elements (2):
Annotation
This is used to specify the QName pattern in the
attribute service-name-pattern and port-name-pattern in
the handler-chain element
For example, the various forms acceptable here for
service-name-pattern attribute in handler-chain element
are :
Exact Name: service-name-pattern="ns1:EchoService"
In this case, handlers specified in this
handler-chain element will apply to all ports with
this exact service name. The namespace prefix must
have been declared in a namespace declaration
attribute in either the start-tag of the element
where the prefix is used or in an an ancestor
element (i.e. an element in whose content the
prefixed markup occurs)
Pattern : service-name-pattern="ns1:EchoService*"
In this case, handlers specified in this
handler-chain element will apply to all ports whose
Service names are like EchoService1, EchoServiceFoo
etc. The namespace prefix must have been declared in
a namespace declaration attribute in either the
start-tag of the element where the prefix is used or
in an an ancestor element (i.e. an element in whose
content the prefixed markup occurs)
Wild Card : service-name-pattern="*"
In this case, handlers specified in this handler-chain
element will apply to ports of all service names.
The same can be applied to port-name attribute in
handler-chain element.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:service-ref_qname-pattern (restriction) |
Derivation: |
restriction of xsd:token |
Facets: |
pattern: |
\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*? |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This is used to specify the QName pattern in the
attribute service-name-pattern and port-name-pattern in
the handler-chain element
For example, the various forms acceptable here for
service-name-pattern attribute in handler-chain element
are :
Exact Name: service-name-pattern="ns1:EchoService"
In this case, handlers specified in this
handler-chain element will apply to all ports with
this exact service name. The namespace prefix must
have been declared in a namespace declaration
attribute in either the start-tag of the element
where the prefix is used or in an an ancestor
element (i.e. an element in whose content the
prefixed markup occurs)
Pattern : service-name-pattern="ns1:EchoService*"
In this case, handlers specified in this
handler-chain element will apply to all ports whose
Service names are like EchoService1, EchoServiceFoo
etc. The namespace prefix must have been declared in
a namespace declaration attribute in either the
start-tag of the element where the prefix is used or
in an an ancestor element (i.e. an element in whose
content the prefixed markup occurs)
Wild Card : service-name-pattern="*"
In this case, handlers specified in this handler-chain
element will apply to ports of all service names.
The same can be applied to port-name attribute in
handler-chain element.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
</xsd:restriction>
</xsd:simpleType>
simpleType "javaee:web-app-versionType"
Namespace: |
|
Defined: |
|
Used: |
|
| Simple Content Model |
| "2.5" |
All Direct / Indirect Based Attributes (1):
-
Known Usage Locations
- As direct type of attributes within complexTypes (1):
Annotation
This type contains the recognized versions of
web-application supported. It is used to designate the
version of the web application.
Type Definition Detail
| Type Derivation Tree xsd:token javaee:web-app-versionType (restriction) |
Derivation: |
restriction of xsd:token |
Facets: |
|
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This type contains the recognized versions of
web-application supported. It is used to designate the
version of the web application.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:token">
<xsd:enumeration value="2.5"/>
</xsd:restriction>
</xsd:simpleType>
group "javaee:descriptionGroup"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 3 elements |
Used: |
|
Content Elements (3):
-
Known Usage Locations
Annotation
This group keeps the usage of the contained description related
elements consistent across Java EE deployment descriptors.
All elements may occur multiple times with different languages,
to support localization of the content.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This group keeps the usage of the contained description related
elements consistent across Java EE deployment descriptors.
All elements may occur multiple times with different languages,
to support localization of the content.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
group "javaee:jndiEnvironmentRefsGroup"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 10 elements |
Used: |
|
| Complex Content Model |
| javaee:env-entry*, javaee:ejb-ref*, javaee:ejb-local-ref*, javaee:service-ref*, javaee:resource-ref*, javaee:resource-env-ref*, javaee:message-destination-ref*, javaee:persistence-context-ref*, javaee:persistence-unit-ref*, javaee:post-construct*, javaee:pre-destroy* |
Content Elements (11):
-
Known Usage Locations
Annotation
This group keeps the usage of the contained JNDI environment
reference elements consistent across Java EE deployment descriptors.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This group keeps the usage of the contained JNDI environment
reference elements consistent across Java EE deployment descriptors.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
</xsd:sequence>
</xsd:group>
Content Element Detail
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source)
-
XML Source (see within schema source) <xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
group "javaee:resourceGroup"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 2 elements |
Used: |
|
Content Elements (2):
-
Known Usage Locations
Annotation
This group collects elements that are common to all the
JNDI resource elements.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
This group collects elements that are common to all the
JNDI resource elements.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail
-
XML Source (see within schema source)
-
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
XML Source (see within schema source) <xsd:annotation>
<xsd:documentation>
<![CDATA[
A product specific name that this resource should be
mapped to. The name of this resource, as defined by the
resource's name element or defaulted, is a name that is
local to the application component using the resource.
(It's a name in the JNDI java:comp/env namespace.) Many
application servers provide a way to map these local
names to names of resources known to the application
server. This mapped name is often a global JNDI name,
but may be a name of any form.
Application servers are not required to support any
particular form or type of mapped name, nor the ability
to use mapped names. The mapped name is
product-dependent and often installation-dependent. No
use of a mapped name is portable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
group "javaee:service-refGroup"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definition of 1 element |
Used: |
|
Content Elements (1):
-
Known Usage Locations
- In definitions of other model groups (1):
XML Source (see within schema source) <xsd:sequence>
<xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
</xsd:sequence>
</xsd:group>
Content Element Detail
-
XML Source (see within schema source) <xsd:key name="service-ref_handler-name-key">
<xsd:annotation>
<xsd:documentation>
Defines the name of the handler. The name must be unique
within the module.
</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="javaee:handler"/>
<xsd:field xpath="javaee:handler-name"/>
</xsd:key>
</xsd:element>
Namespace "http://www.w3.org/XML/1998/namespace"
Targeting Schemas (1):
-
Components:
-
| Schema Summary |
| xml.xsd |
See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace. Target Namespace: -
Components: -
Schema Location: -
Imported by Schema: -
|
| Global Attribute Summary |
| xml:base |
See http://www.w3.org/TR/xmlbase/ for
information about this attribute.
Type: |
xs:anyURI |
Defined: |
|
Used: |
|
|
| xml:id |
See http://www.w3.org/TR/xml-id/ for
information about this attribute.
Type: |
xs:ID |
Defined: |
|
Used: |
|
|
| xml:lang |
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Defined: |
|
Used: |
|
|
| xml:space |
|
| Attribute Group Summary |
| xml:specialAttrs |
Content: |
|
Defined: |
|
Includes: |
definitions of 4 attributes |
Used: |
never |
|
XML Schema "xml.xsd"
Target Namespace:
-
Components:
-
Schema Location:
-
Imported by Schema:
-
Annotation
Annotation 1:
See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace.
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
Note that local names in this namespace are intended to be defined
only by the World Wide Web Consortium or its subgroups. The
following names are currently defined in this namespace and should
not be used with conflicting semantics by any Working Group,
specification, or document instance:
base (as an attribute name): denotes an attribute whose value
provides a URI to be used as the base for interpreting any
relative URIs in the scope of the element on which it
appears; its value is inherited. This name is reserved
by virtue of its definition in the XML Base specification.
id (as an attribute name): denotes an attribute whose value
should be interpreted as if declared to be of type ID.
This name is reserved by virtue of its definition in the
xml:id specification.
lang (as an attribute name): denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.
space (as an attribute name): denotes an attribute whose
value is a keyword indicating what whitespace processing
discipline is intended for the content of the element; its
value is inherited. This name is reserved by virtue of its
definition in the XML specification.
Father (in any context at all): denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
In appreciation for his vision, leadership and dedication
the W3C XML Plenary on this 10th day of February, 2000
reserves for Jon Bosak in perpetuity the XML name
xml:Father
Annotation 2:
This schema defines attributes and an attribute group
suitable for use by
schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
attributes on elements they define.
To enable this, such a schema must import this schema
for the XML namespace, e.g. as follows:
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
Subsequently, qualified reference to any of the attributes
or the group defined below will have the desired effect, e.g.
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
will define a type which will schema-validate an instance
element with any of those attributes
Annotation 3:
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2007/08/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself, or with the XML namespace itself. In other words, if the XML
Schema or XML namespaces change, the version of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2007/08/xml.xsd will not change.
| Global Attribute Summary |
| xml:base |
See http://www.w3.org/TR/xmlbase/ for
information about this attribute.
|
| xml:id |
See http://www.w3.org/TR/xml-id/ for
information about this attribute.
|
| xml:lang |
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility.
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Used: |
|
|
| xml:space |
|
| Attribute Group Summary |
| xml:specialAttrs |
Content: |
|
Includes: |
definitions of 4 attributes |
Used: |
never |
|
XML Source
<?xml version="1.0"?>
<xs:annotation>
<xs:documentation>
See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace.
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
Note that local names in this namespace are intended to be defined
only by the World Wide Web Consortium or its subgroups. The
following names are currently defined in this namespace and should
not be used with conflicting semantics by any Working Group,
specification, or document instance:
base (as an attribute name): denotes an attribute whose value
provides a URI to be used as the base for interpreting any
relative URIs in the scope of the element on which it
appears; its value is inherited. This name is reserved
by virtue of its definition in the XML Base specification.
id (as an attribute name): denotes an attribute whose value
should be interpreted as if declared to be of type ID.
This name is reserved by virtue of its definition in the
xml:id specification.
lang (as an attribute name): denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.
space (as an attribute name): denotes an attribute whose
value is a keyword indicating what whitespace processing
discipline is intended for the content of the element; its
value is inherited. This name is reserved by virtue of its
definition in the XML specification.
Father (in any context at all): denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
In appreciation for his vision, leadership and dedication
the W3C XML Plenary on this 10th day of February, 2000
reserves for Jon Bosak in perpetuity the XML name
xml:Father
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
This schema defines attributes and an attribute group
suitable for use by
schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
attributes on elements they define.
To enable this, such a schema must import this schema
for the XML namespace, e.g. as follows:
<schema . . .>
. . .
<import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
Subsequently, qualified reference to any of the attributes
or the group defined below will have the desired effect, e.g.
<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>
will define a type which will schema-validate an instance
element with any of those attributes
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2007/08/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself, or with the XML namespace itself. In other words, if the XML
Schema or XML namespaces change, the version of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2007/08/xml.xsd will not change.
</xs:documentation>
</xs:annotation>
<xs:attribute name="lang"> <xs:annotation>
<xs:documentation>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility. See
RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
at http://www.iana.org/assignments/lang-tag-apps.htm for
further information.
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union memberTypes="xs:language">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value=""/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="space"> <xs:simpleType>
<xs:restriction base="xs:NCName">
<xs:enumeration value="default"/>
<xs:enumeration value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="base" type="xs:anyURI"> <xs:annotation>
<xs:documentation>
See http://www.w3.org/TR/xmlbase/ for
information about this attribute.
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="id" type="xs:ID"> <xs:annotation>
<xs:documentation>
See http://www.w3.org/TR/xml-id/ for
information about this attribute.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:attributeGroup>
</xs:schema>
attribute "xml:base"
Namespace: |
|
Type: |
xs:anyURI |
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
base |
= |
xs:anyURI |
| ...> |
Known Usage Locations
Annotation
See http://www.w3.org/TR/xmlbase/ for
information about this attribute.
XML Source (see within schema source) <xs:attribute name="base" type="xs:anyURI"> <xs:annotation>
<xs:documentation>
See http://www.w3.org/TR/xmlbase/ for
information about this attribute.
</xs:documentation>
</xs:annotation>
</xs:attribute>
attribute "xml:id"
Namespace: |
|
Type: |
xs:ID |
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
id |
= |
xs:ID |
| ...> |
Known Usage Locations
Annotation
See http://www.w3.org/TR/xml-id/ for
information about this attribute.
XML Source (see within schema source) <xs:attribute name="id" type="xs:ID"> <xs:annotation>
<xs:documentation>
See http://www.w3.org/TR/xml-id/ for
information about this attribute.
</xs:documentation>
</xs:annotation>
</xs:attribute>
attribute "xml:lang"
Namespace: |
|
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
lang |
= |
(xs:language | "") |
| ...> |
Known Usage Locations
Annotation
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility. See
RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
at http://www.iana.org/assignments/lang-tag-apps.htm for
further information.
The union allows for the 'un-declaration' of xml:lang with
the empty string.
Anonymous Type Detail
| Type Derivation Tree union of (xs:language | restriction of xs:string) simpleType |
Member Types
xs:language
anonymous simpleType:
Derivation: |
restriction of xs:string |
Facets: |
|
XML Source (see within schema source) <xs:attribute name="lang"> <xs:annotation>
<xs:documentation>
Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility. See
RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
at http://www.iana.org/assignments/lang-tag-apps.htm for
further information.
The union allows for the 'un-declaration' of xml:lang with
the empty string.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union memberTypes="xs:language">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value=""/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
</xs:attribute>
attribute "xml:space"
Namespace: |
|
Type: |
|
Defined: |
|
Used: |
|
| XML Representation Summary |
| <... |
| |
space |
= |
("default" | "preserve") |
| ...> |
Known Usage Locations
Anonymous Type Detail
| Type Derivation Tree xs:NCName simpleType (restriction) |
Derivation: |
restriction of xs:NCName |
Facets: |
enumeration: |
"default", "preserve" |
|
XML Source (see within schema source) <xs:attribute name="space"> <xs:simpleType>
<xs:restriction base="xs:NCName">
<xs:enumeration value="default"/>
<xs:enumeration value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
attributeGroup "xml:specialAttrs"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
definitions of 4 attributes |
Used: |
never |
XML Source (see within schema source) </xs:attributeGroup>
Attribute Detail
-
Type: |
xs:anyURI, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
-
Type: |
xs:ID, predefined |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
-
Type: |
anonymous (union of (xs:language | restriction of xs:string)) |
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
-
Type: |
|
Use: |
optional |
Defined: |
|
XML Source (see within schema source)
This XML schema documentation has been generated with DocFlex/XML (Kit) 1.7.0 using DocFlex/XML | XSDDoc 2.0.0 template set.DocFlex/XML (Kit) is a reduced edition of DocFlex/XML, which is a universal template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this tool offers highly sophisticated data querying and formatting capabilities enough to develop in a couple of months a full-blown specialized documentation generator, whose programming in ordinary way (e.g. using Java & XSLT) would take years! DocFlex/XML | XSDDoc is such an application of DocFlex/XML. This is just a set of templates. However, it implements a top-class XML Schema documentation generator you will hardly find anywhere else! Thanks to the whole technology, it automatically supports framed multi-file HTML, single-file HTML and RTF output formats. (More formats are coming). If you need to convert your XML data into a clear-cut nice-looking documentation in the form of web-ready hypertext HTML or printable unmatched quality RTF friendly to open with MS Word / OpenOffice.org, DocFlex/XML may be a cheap, quick and effective solution exactly for your task! |