diff options
Diffstat (limited to 'bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_5.xsd')
| -rw-r--r-- | bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_5.xsd | 304 |
1 files changed, 0 insertions, 304 deletions
diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_5.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_5.xsd deleted file mode 100644 index e740827b74..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_5.xsd +++ /dev/null @@ -1,304 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" - targetNamespace="http://java.sun.com/xml/ns/javaee" - xmlns:javaee="http://java.sun.com/xml/ns/javaee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="5"> - <xsd:annotation> - <xsd:documentation> - @(#)application-client_5.xsds 1.26 02/17/06 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003-2005 Sun Microsystems, Inc. - 4150 Network Circle - Santa Clara, California 95054 - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the application client 5 - deployment descriptor. The deployment descriptor must - be named "META-INF/application-client.xml" in the - application client's jar file. All application client - deployment descriptors must indicate the application - client schema by using the Java EE namespace: - - http://java.sun.com/xml/ns/javaee - - and indicate the version of the schema by - using the version element as shown below: - - <application-client xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/javaee - http://java.sun.com/xml/ns/javaee/application-client_5.xsd" - version="5"> - ... - </application-client> - - 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/application-client_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:include schemaLocation="javaee_5.xsd"/> - - -<!-- **************************************************** --> - - <xsd:element name="application-client" type="javaee:application-clientType"> - <xsd:annotation> - <xsd:documentation> - - The application-client element is the root element of an - application client deployment descriptor. The application - client deployment descriptor describes the EJB components - and external resources referenced by the application - client. - - </xsd:documentation> - </xsd:annotation> - - <xsd:unique name="env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of an - application client's environment entry. The name is a JNDI - name relative to the java:comp/env context. The name must - be unique within an application client. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:env-entry"/> - <xsd:field xpath="javaee:env-entry-name"/> - </xsd:unique> - - <xsd:unique name="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 application - client's environment and is relative to the - java:comp/env context. The name must be unique within the - application client. - - 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="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 an application client. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-ref"/> - <xsd:field xpath="javaee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="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 application client - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - application client. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-env-ref"/> - <xsd:field xpath="javaee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="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 message destination reference name used in the - application client code. The name is a JNDI name - relative to the java:comp/env context and must be unique - within an application client. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:message-destination-ref"/> - <xsd:field xpath="javaee:message-destination-ref-name"/> - </xsd:unique> - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="application-clientType"> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="env-entry" - type="javaee:env-entryType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-ref" - type="javaee:ejb-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:group ref="javaee:service-refGroup"/> - <xsd:element name="resource-ref" - type="javaee:resource-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="resource-env-ref" - type="javaee:resource-env-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="message-destination-ref" - type="javaee:message-destination-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="persistence-unit-ref" - type="javaee:persistence-unit-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="post-construct" - type="javaee:lifecycle-callbackType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="pre-destroy" - type="javaee:lifecycle-callbackType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="callback-handler" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The callback-handler element names a class provided by - the application. The class must have a no args - constructor and must implement the - javax.security.auth.callback.CallbackHandler - interface. The class will be instantiated by the - application client container and used by the container - to collect authentication information from the user. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="message-destination" - type="javaee:message-destinationType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="version" - type="javaee:dewey-versionType" - fixed="5" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 5. - - </xsd:documentation> - </xsd:annotation> - - </xsd:attribute> - - <xsd:attribute name="metadata-complete" type="xsd:boolean"> - <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:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - |