@(#)application_1_4.xsds 1.13 02/11/03 Copyright 2002 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, California 94303, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and other countries. This document and the technology which it describes are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE, JavaServer Pages, Enterprise JavaBeans and the Java Coffee Cup logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Federal Acquisitions: Commercial Software - Government Users Subject to Standard License Terms and Conditions. ... The instance documents may indicate the published version of the schema using the xsi:schemaLocation attribute for J2EE namespace with the following location: http://java.sun.com/xml/ns/j2ee/application_1_4.xsd ]]> The following conventions apply to all J2EE 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. The application element is the root element of a J2EE application deployment descriptor. The context-root element content must be unique in the ear. The security-role-name element content must be unique in the ear. The applicationType defines the structure of the application. The application deployment descriptor must have one module element for each J2EE module in the application package. A module element is defined by moduleType definition. The required value for the version is 1.4. The moduleType defines a single J2EE module and contains a connector, ejb, java, or web element, which indicates the module type and contains a path to the module file, and an optional alt-dd element, which specifies an optional URI to the post-assembly version of the deployment descriptor. The connector element specifies the URI of a resource adapter archive file, relative to the top level of the application package. The ejb element specifies the URI of an ejb-jar, relative to the top level of the application package. The java element specifies the URI of a java application client module, relative to the top level of the application package. The alt-dd element specifies an optional URI to the post-assembly version of the deployment descriptor file for a particular J2EE module. The URI must specify the full pathname of the deployment descriptor file relative to the application's root directory. If alt-dd is not specified, the deployer must read the deployment descriptor from the default location and file name required by the respective component specification. The webType defines the web-uri and context-root of a web application module. The web-uri element specifies the URI of a web application file, relative to the top level of the application package. The context-root element specifies the context root of a web application.