Apache Geronimo >  Index >  Development >  XML Schemas >  Apache Geronimo v2.1 XML Schemas User List | Dev List | Wiki | Issue Tracker  
  Overview
Home
License
ASF
Project Policies
Downloads
Documentation
News Archive
  Search
Powered by Google Search
  Community
Events
Get Involved
Committers
Mailing Lists
Discussion Forums
IRC
FAQ
Wiki
Found a Bug?
Service and Support
ASF Sponsorship
ASF Thanks!
  Development
Javadoc
XML Schemas
Source Code
Coding Standards
Issue Tracker
Related Projects
Sample Applications
  Subprojects
Development Tools
GBuild
GShell
XBean
  geronimo-connector-1.2.xsd Apache Geronimo v2.1 XML Schemas   geronimo-application-2.0.xsd 

Documentation for geronimo-application-client-2.0

Table of Contents

top

Schema Document Properties

Target Namespace http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
Version 1.0
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 namespace.
  • By default, local attribute declarations have no namespace.
Schema Composition
  • This schema imports schema(s) from the following namespace(s):
    • http://geronimo.apache.org/xml/ns/naming-1.2 (at geronimo-naming-1.2.xsd)
    • http://geronimo.apache.org/xml/ns/security-2.0 (at geronimo-security-2.0.xsd)
    • http://geronimo.apache.org/xml/ns/j2ee/connector-1.2 (at geronimo-connector-1.2.xsd)
    • http://geronimo.apache.org/xml/ns/deployment-1.2 (at geronimo-module-1.2.xsd)
Documentation This is an XML Schema Definition for Geronimo Java application client deployment plan. In case the Java application client deployment plan is provided internally in the java archive, it should be named META-INF/geronimo-application-client.xml. In case the java application client deployment plan is provided externally, the deployment descriptor can be named anything and provided to the deploy tool. All the Java application client deployment plan must specify the top level element as application-client with namespace specified as xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0". The default location for this document is http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0

Declared Namespaces

Prefix Namespace
xml http://www.w3.org/XML/1998/namespace
geronimo http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0
xs http://www.w3.org/2001/XMLSchema
naming http://geronimo.apache.org/xml/ns/naming-1.2
connector http://geronimo.apache.org/xml/ns/j2ee/connector-1.2
security http://geronimo.apache.org/xml/ns/security-2.0
sys http://geronimo.apache.org/xml/ns/deployment-1.2
Schema Component Representation
<xs:schema targetNamespace="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
<xs:import namespace="http://geronimo.apache.org/xml/ns/naming-1.2" schemaLocation="geronimo-naming-1.2.xsd"/>
<xs:import namespace="http://geronimo.apache.org/xml/ns/security-2.0" schemaLocation="geronimo-security-2.0.xsd"/>
<xs:import namespace="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2" schemaLocation="geronimo-connector-1.2.xsd"/>
<xs:import namespace="http://geronimo.apache.org/xml/ns/deployment-1.2" schemaLocation="geronimo-module-1.2.xsd"/>
...
</xs:schema>
top

Global Declarations

Element: application-client

Name application-client
Type geronimo:application-clientType
Nillable no
Abstract no
Documentation The root element for Geronimo Java application client deployment plan, this element should always exist in instance documents. It mirrors the application-client defined by application-client_1_4.xsd. It specifies the references for the java application client modules. These references could be reference to external gbeans, ejb modules, service modules, resources, or security principals.
Logical Diagram
h-1054520012 h-310438740 h414327002 h671369440 h-334859080 h1804910263 h1639631831 h1355340165 h-1044628899 h85315698
XML Instance Representation
<geronimo:application-client>
<sys:client-environment> ... </sys:client-environment> [1]

'Reference to client-environment element defined in imported \"geronimo-module-1.2.xsd\"'

<sys:server-environment> ... </sys:server-environment> [1]

'Reference to server-environment element defined in imported \"geronimo-module-1.2.xsd\"'

<naming:gbean-ref> ... </naming:gbean-ref> [0..*]

'Reference to gbean-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:ejb-ref> ... </naming:ejb-ref> [0..*]

'Reference to ejb-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:service-ref> ... </naming:service-ref> [0..*]

'Reference to service-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:resource-ref> ... </naming:resource-ref> [0..*]

'Reference to resource-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:resource-env-ref> ... </naming:resource-env-ref> [0..*]

'Reference to resource-env-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:message-destination> ... </naming:message-destination> [0..*]

'Reference to message-destination element defined in imported \"geronimo-naming-1.2.xsd\"'

<security:default-subject> ... </security:default-subject> [0..1]

'Reference to default-subject element defined in imported \"geronimo-security-2.0.xsd\" This is the subject run under if you are not logged in.'

Start Sequence [0..1]
<geronimo:realm-name> xs:string </geronimo:realm-name> [1]

'The realm-name element names the security realm used for JAAS login'

<geronimo:callback-handler> xs:string </geronimo:callback-handler> [0..1]

'The callback-handler element specifies the name of a callback class provided by the application for JAAS authentication. This class must implement the javax.security.auth.callback.CallbackHandler interface and follow its specification, as this class will be used by the application client container to collect authentication information from the user.'

End Sequence
<geronimo:resource> geronimo:resourceType </geronimo:resource> [0..*]

'The resource element names contains the definition of all the module-scoped connector resources. The connector resource can be both external and internal to the application client.'

<sys:service> ... </sys:service> [0..*]

'Reference to service element defined in imported \"geronimo-module-1.2.xsd\"'

</geronimo:application-client>
Diagram
h-1054520012 h-310438740 h414327002 h671369440 h-334859080 h1804910263 h1639631831 h1355340165 h-1044628899 h52427085 h85315698
Schema Component Representation
<xs:element name="application-client" type=" geronimo:application-clientType "/>
top

Global Definitions

Complex Type: application-clientType

Super-types: None
Sub-types: None
Name application-clientType
Used by (from the same schema document) Element application-client
Abstract no
XML Instance Representation
<...>
<sys:client-environment> ... </sys:client-environment> [1]

'Reference to client-environment element defined in imported \"geronimo-module-1.2.xsd\"'

<sys:server-environment> ... </sys:server-environment> [1]

'Reference to server-environment element defined in imported \"geronimo-module-1.2.xsd\"'

<naming:gbean-ref> ... </naming:gbean-ref> [0..*]

'Reference to gbean-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:ejb-ref> ... </naming:ejb-ref> [0..*]

'Reference to ejb-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:service-ref> ... </naming:service-ref> [0..*]

'Reference to service-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:resource-ref> ... </naming:resource-ref> [0..*]

'Reference to resource-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:resource-env-ref> ... </naming:resource-env-ref> [0..*]

'Reference to resource-env-ref element defined in imported \"geronimo-naming-1.2.xsd\"'

<naming:message-destination> ... </naming:message-destination> [0..*]

'Reference to message-destination element defined in imported \"geronimo-naming-1.2.xsd\"'

<security:default-subject> ... </security:default-subject> [0..1]

'Reference to default-subject element defined in imported \"geronimo-security-2.0.xsd\" This is the subject run under if you are not logged in.'

Start Sequence [0..1]
<geronimo:realm-name> xs:string </geronimo:realm-name> [1]

'The realm-name element names the security realm used for JAAS login'

<geronimo:callback-handler> xs:string </geronimo:callback-handler> [0..1]

'The callback-handler element specifies the name of a callback class provided by the application for JAAS authentication. This class must implement the javax.security.auth.callback.CallbackHandler interface and follow its specification, as this class will be used by the application client container to collect authentication information from the user.'

End Sequence
<geronimo:resource> geronimo:resourceType </geronimo:resource> [0..*]

'The resource element names contains the definition of all the module-scoped connector resources. The connector resource can be both external and internal to the application client.'

<sys:service> ... </sys:service> [0..*]

'Reference to service element defined in imported \"geronimo-module-1.2.xsd\"'

</...>
Diagram
h-1054520012 h-310438740 h414327002 h671369440 h-334859080 h1804910263 h1639631831 h1355340165 h-1044628899 h52427085 h85315698
Schema Component Representation
<xs:complexType name="application-clientType">
<xs:sequence>
<xs:element ref=" sys:client-environment "/>
<xs:element ref=" sys:server-environment "/>
<xs:element ref=" naming:gbean-ref " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" naming:ejb-ref " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" naming:service-ref " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" naming:resource-ref " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" naming:resource-env-ref " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" naming:message-destination " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" security:default-subject " minOccurs="0"/>
<xs:sequence minOccurs="0">
<xs:element name="realm-name" type=" xs:string "/>
<xs:element name="callback-handler" type=" xs:string " minOccurs="0"/>
</xs:sequence>
<xs:element name="resource" type=" geronimo:resourceType " minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref=" sys:service " minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
top

Complex Type: resourceType

Super-types: None
Sub-types: None
Name resourceType
Used by (from the same schema document) Complex Type application-clientType
Abstract no
XML Instance Representation
<...>
Start Choice [1]
<geronimo:external-rar> sys:patternType </geronimo:external-rar> [1]

'The external-rar is a Module ID of the resource adapter in the Geronimo repository.'

<geronimo:internal-rar> xs:string </geronimo:internal-rar> [1]

'The internal-rar is a Module ID of the resource adapter in the client module.'

End Choice
<connector:connector> ... </connector:connector> [1]

'This element contains the contents of the Resource Group deployment plan. The content is no different that the content of the deployment plan would have been for the server-wide or application-scoped resource group.'

</...>
Diagram
h284462437 h-1015094
Schema Component Representation
<xs:complexType name="resourceType">
<xs:sequence>
<xs:choice>
<xs:element name="external-rar" type=" sys:patternType "/>
<xs:element name="internal-rar" type=" xs:string "/>
</xs:choice>
<xs:element ref=" connector:connector "/>
</xs:sequence>
</xs:complexType>
top

Legend

Complex Type:

Schema Component Type

AusAddress

Schema Component Name
Super-types: Address < AusAddress (by extension)
Sub-types:
  • QLDAddress (by restriction)
If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.
Name AusAddress
Abstract no
The table above displays the properties of this schema component.
XML Instance Representation
<... country="Australia" >
<unitNo> string </unitNo> [0..1]
<houseNo> string </houseNo> [1]
<street> string </street> [1]
Start Choice [1]
<city> string </city> [1]
<town> string </town> [1]
End Choice
<state> AusStates </state> [1]
<postcode> string <<pattern = [1-9][0-9]{3}>> </postcode> [1] ?
</...>

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
<complexType name="AusAddress">
<complexContent>
<extension base=" Address ">
<sequence>
<element name="state" type=" AusStates "/>
<element name="postcode">
<simpleType>
<restriction base=" string ">
<pattern value="[1-9][0-9]{3}"/>
</restriction>
</simpleType>
</element>
</sequence>
<attribute name="country" type=" string " fixed="Australia"/>
</extension>
</complexContent>
</complexType>
The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)
top

Glossary

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: http://www.w3.org/TR/xmlschema-1/#element-all.

Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See: http://www.w3.org/TR/xmlschema-1/#element-choice.

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: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

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: http://www.w3.org/TR/xmlschema-1/#Model_Groups.

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 http://www.w3.org/2001/XMLSchema-instance 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: http://www.w3.org/TR/xmlschema-1/#cNotation_Declarations.

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: http://www.w3.org/TR/xmlschema-1/#element-sequence.

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: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.

top

Copyright © 2003-2008, The Apache Software Foundation