Child pages
  • geronimo-application-1.1.xsd
Skip to end of metadata
Go to start of metadata


The following article describes the XML Schema for the geronimo-application.xsd deployment descriptor .In order to deploy an EAR application in Geronimo,there should be a Geronimo specific deployment plan for it called "geronimo-application.xml".The deployment descriptor must be named "META-INF/geronimo-application.xml" in the application's EAR file.
The article organized into the following sections : -

Geronimo Application XML Schema Document


Schema Document Properties

Target Namespace
As all the other application deployment descriptors must indicate
the application schema by using the J2EE namespace the
geronimo-application also uses this J2EE namespace


1.0 - The version indicates the published version ofthe schema

Element and Attribute Namespaces

Global element and attribute declarations belong to this schema's
target namespace.
By default, local element declarations belong to this schema's target
By default, local attribute declarations have no namespace.

Schema Composition

This schema imports schema(s) from the following namespace(s):



Declared Namespaces





The namespace whose name is

is bound by definition to the prefix xml: according to Namespaces in XML, W3C Recommendation 14 Jan 1999


This is the target name space defined for Geronimo EAR applications


This schema describes Common security elements used by other plans in Security Mapping module.


This schema Used to deploy new services in Geronimo in a standalone plan, and also contains common elements used by many other plans and the module type is Server Plans & Common Elements


This document describes the XML Schema namespace. It also contains a directory of links to these related resources, using Resource Directory Description Language

Schema Component Representation

Global Declarations

This section highlights the application element declaration that is available for use in the content models throughout the schema.

Element: Application












The application element is the root element of a
J2EE application deployment descriptor in Geronimo

XML Instance Representation
Schema Component Representation

Global Definitions

[This section highlights the complex types (an XML element that contains other elements and/or attributes)
which can be be referenced within the same schema of by other schemas.]

Complex Type: applicationType










The applicationType defines the structure of the application in geronimo.
The application deployment descriptor must have one module element for each
J2EE module in the application package. A module element is defined by moduleType

XML Instance Representation: applicationType
Schema Component Representation: applicationType

Complex Type: ext-moduleType










Mirrors the moduleType defined by application_1_4.xsd and adds an optional alt-dd element
defining a Geronimo specific deploy descriptors.

XML Instance Representation: ext-ModuleType
Schema Component Representation: ext-ModuleType

Complex Type: string


xs:token < string (by extension)








Mirrors j2ee:string.

XML Instance Representation: string
Schema Component Representation: string


Complex Type:


Schema Component Type

Schema Component Name


Address < AusAddress (by extension)


QLDAddress (by restriction)

If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.





The table above displays the properties of this schema component.

XML Instance Representation

The XML Instance Representation table above shows the schema component's content as an XML instance.

  • The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
  • Model group information are shown in gray, e.g. Start Choice ... End Choice.
  • For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
  • If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
  • Otherwise, the type of the element/attribute is displayed.
    • If the element/attribute's type is in the schema, a link is provided to it.
    • For local simple type definitions, the constraints are displayed in angle brackets, e.g. <pattern = [1-9][0-9]{3}/>
  • If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Schema Component Representation

The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)


Abstract (Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.

All Model Group Child elements can be provided in any order in instances. See:

Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See:

Collapse Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.

Disallowed Substitutions (Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.

Key Constraint Like Uniqueness Constraint, but additionally requires that the specified value(s) must be provided. See:

Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See:

Model Group Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See:

Nillable (Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.

Notation A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See:

Preserve Whitespace Policy Preserve whitespaces exactly as they appear in instances.

Prohibited Derivations (Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.

Prohibited Substitutions (Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.

Replace Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32).

Sequence Model Group Child elements and model groups must be provided in the specified order in instances. See:

Substitution Group Elements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.

Substitution Group Exclusions (Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.

Target Namespace The target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
Uniqueness Constraint Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See:

  • No labels