diff options
Diffstat (limited to 'bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas')
36 files changed, 0 insertions, 31806 deletions
diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_2.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_2.dtd deleted file mode 100644 index 6c58cc9363..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_2.dtd +++ /dev/null @@ -1,292 +0,0 @@ -<!-- -Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - - - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ -Copyright 1999 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - -<!-- -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. ---> -<!ELEMENT application-client (icon?, display-name, description?, env-entry*, -ejb-ref*, resource-ref*)> - -<!-- -The description element is used to provide text describing the parent element. -The description element should include any information that the -application-client file producer wants to provide to the consumer of the -application-client file (i.e., to the Deployer). Typically, the tools used by -the application-client file consumer will display the description when -processing the parent element that contains the description. ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be displayed -by tools. ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb-link element is used in the ejb-ref element to specify that an EJB -reference is linked to an enterprise bean in the encompassing J2EE Application -package. The value of the ejb-link element must be the ejb-name of an enterprise -bean in the same J2EE Application package. Used in: ejb-ref -Example: <ejb-link>EmployeeRecord</ejb-link> ---> -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ejb-ref element is used for the declaration of a reference to an enterprise -bean's home. The declaration consists of an optional description; the EJB -reference name used in the code of the referencing application client; the -expected type of the referenced enterprise bean; the expected home and remote -interfaces of the referenced enterprise bean; and an optional ejb-link -information. The optional ejb-link element is used to specify the referenced -enterprise bean. ---> -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, remote, -ejb-link?)> - -<!-- -The ejb-ref-name element contains the name of an EJB reference. The EJB -reference is an entry in the application client's environment. It is recommended -that name is prefixed with "ejb/". Used in: ejb-ref -Example: <ejb-ref-name>ejb/Payroll</ejb-ref-name> ---> -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected type of the referenced enterprise -bean. The ejb-ref-type element must be one of the following: -<ejb-ref-type>Entity</ejb-ref-type> -<ejb-ref-type>Session</ejb-ref-type> -Used in: ejb-ref ---> -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- -The env-entry element contains the declaration of an application client's -environment entries. The declaration consists of an optional description, the -name of the environment entry, and an optional value. ---> -<!ELEMENT env-entry (description?, env-entry-name, env-entry-type, -env-entry-value?)> - -<!-- -The env-entry-name element contains the name of an application client's -environment entry. Used in: env-entry -Example: <env-entry-name>EmployeeAppDB</env-entry-name> ---> -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-type element contains the fully-qualified Java type of the -environment entry value that is expected by the application client's code. The -following are the legal values of env-entry-type: java.lang.Boolean, -java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, -java.lang.Short, java.lang.Long, and java.lang.Float. - -Used in: env-entry - -Example: -<env-entry-type>java.lang.Boolean</env-entry-type> ---> -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The env-entry-value element contains the value of an application client'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. - -Used in: env-entry - -Example: -<env-entry-value>/datasources/MyDatabase</env-entry-value> ---> -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The home element contains the fully-qualified name of the enterprise bean's home -interface. -Used in: ejb-ref -Example: <home>com.aardvark.payroll.PayrollHome</home> ---> -<!ELEMENT home (#PCDATA)> - -<!-- -The icon element contains a small-icon and large-icon element which specify the -URIs for a small and a large GIF or JPEG icon image used to represent the -application client in a GUI tool. ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -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 application-client jar -file. The image must be either in the JPEG or GIF format, and the file name must -end with the suffix ".jpg" or ".gif" respectively. The icon can be used by -tools. -Example: -<large-icon>lib/images/employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The remote element contains the fully-qualified name of the enterprise bean's -remote interface. -Used in: ejb-ref -Example: -<remote>com.wombat.empl.EmployeeService</remote> ---> -<!ELEMENT remote (#PCDATA)> - -<!-- -The res-auth element specifies whether the enterprise bean code signs on -programmatically to the resource manager, or whether the Container will sign on -to the resource manager on behalf of the bean. In the latter case, the Container -uses information that is supplied by the Deployer. -The value of this element must be one of the two following: -<res-auth>Application</res-auth> -<res-auth>Container</res-auth> ---> -<!ELEMENT res-auth (#PCDATA)> - -<!-- -The res-ref-name element specifies the name of the resource factory reference -name. The resource factory reference name is the name of the application -client's environment entry whose value contains the JNDI name of the data -source. -Used in: resource-ref ---> -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-type element specifies the type of the data source. The type is -specified by the Java interface (or class) expected to be implemented by the -data source. -Used in: resource-ref ---> -<!ELEMENT res-type (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of application clients's -reference to an external resource. It consists of an optional description, the -resource factory reference name, the indication of the resource factory type -expected by the application client's code, and the type of authentication (bean -or container). - -Example: -<resource-ref> -<res-ref-name>EmployeeAppDB</res-ref-name> -<res-type>javax.sql.DataSource</res-type> -<res-auth>Container</res-auth> -</resource-ref> ---> -<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth)> -<!-- -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 application-client jar -file. The image must be either in the JPEG or GIF format, and the file name must -end with the suffix ".jpg" or ".gif" respectively. The icon can be used by -tools. -Example: -<small-icon>lib/images/employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The ID mechanism is to allow tools to easily make tool-specific references to -the elements of the deployment descriptor. - --> -<!ATTLIST application-client id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_3.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_3.dtd deleted file mode 100644 index f9d456d504..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_3.dtd +++ /dev/null @@ -1,506 +0,0 @@ -<!-- -Copyright (c) 2000 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 embodied in the product that is 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 in other countries. - -This document and the product to which it pertains are distributed -under licenses restricting their use, copying, distribution, and -decompilation. This document may be reproduced and distributed but may -not be changed 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, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and and -Enterprise JavaBeans 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. - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED -WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR -NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH -DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. - - -_________________________________________________________________________ - -Copyright (c) 2000 Sun Microsystems, Inc., -901 San Antonio Road, -Palo Alto, California 94303, E'tats-Unis. -Tous droits re'serve's. - -Sun Microsystems, Inc. a les droits de proprie'te' intellectuels -relatants a` la technologie incorpore'e dans le produit qui est de'crit -dans ce document. En particulier, et sans la limitation, ces droits de -proprie'te' intellectuels peuvent inclure un ou plus des brevets -ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les -brevets plus supple'mentaires ou les applications de brevet en attente -dans les E'tats-Unis et dans les autres pays. - -Ce produit ou document est prote'ge' par un copyright et distribue' -avec des licences qui en restreignent l'utilisation, la copie, la -distribution, et la de'compilation. Ce documention associe n peut -e^tre reproduite et distribuer, par quelque moyen que ce soit, sans -l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de -licence, le cas e'che'ant. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright et -licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail et and -Enterprise JavaBeans sont des marques de fabrique ou des marques -de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres -pays. - -LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT -EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS -NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A -L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE -CONTREFAC,ON. ---> - -<!-- -This is the XML DTD for the J2EE 1.3 application client deployment -descriptor. All J2EE 1.3 application client deployment descriptors -must include a DOCTYPE of the following form: - - <!DOCTYPE application-client PUBLIC - "-//Sun Microsystems, Inc.//DTD J2EE Application Client 1.3//EN" - "http://java.sun.com/dtd/application-client_1_3.dtd"> - ---> - -<!-- -The following conventions apply to all J2EE deployment descriptor -elements unless indicated otherwise. - -- In elements that contain PCDATA, leading and trailing whitespace - in the data may be ignored. - -- In elements whose value is an "enumerated type", the value is - case sensitive. - -- 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-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. ---> -<!ELEMENT application-client (icon?, display-name, description?, - env-entry*, ejb-ref*, resource-ref*, resource-env-ref*, - callback-handler?)> - -<!-- -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. - -Used in: application-client ---> -<!ELEMENT callback-handler (#PCDATA)> - -<!-- -The description element is used to provide text describing the parent -element. The description element should include any information that -the application client jar file producer wants to provide to the consumer of -the application client jar file (i.e., to the Deployer). Typically, the tools -used by the application client jar file consumer will display the description -when processing the parent element that contains the description. - -Used in: application-client, ejb-ref, env-entry, resource-env-ref, -resource-ref ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -displayed by tools. The display name need not be unique. - -Used in: application-client - -Example: - -<display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb-link element is used in the ejb-ref element -to specify that an EJB reference is linked to an -enterprise bean. - -The name in the ejb-link element is 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 jar file -containing the application client that is referencing the enterprise bean. -This allows multiple enterprise beans with the same ejb-name to be -uniquely identified. - -Used in: ejb-ref - -Examples: - - <ejb-link>EmployeeRecord</ejb-link> - - <ejb-link>../products/product.jar#ProductEJB</ejb-link> - ---> -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ejb-ref element is used for the declaration of a reference to -an enterprise bean's home. The declaration consists of: - - - an optional description - - the EJB reference name used in the code of - the application client that's referencing the enterprise bean - - the expected type of the referenced enterprise bean - - the expected home and remote interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the referenced - enterprise bean - -Used in: application-client ---> -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, - home, remote, ejb-link?)> - -<!-- -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/". - -Used in: ejb-ref - -Example: - -<ejb-ref-name>ejb/Payroll</ejb-ref-name> ---> -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected type of the -referenced enterprise bean. - -The ejb-ref-type element must be one of the following: - - <ejb-ref-type>Entity</ejb-ref-type> - <ejb-ref-type>Session</ejb-ref-type> - -Used in: ejb-ref ---> -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- -The env-entry element contains the declaration of an application client's -environment entry. The declaration consists of an optional -description, the name of the environment entry, and an optional -value. If a value is not specified, one must be supplied -during deployment. - -Used in: application-client ---> -<!ELEMENT env-entry (description?, env-entry-name, env-entry-type, - env-entry-value?)> - -<!-- -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. - -Used in: env-entry - -Example: - -<env-entry-name>minAmount</env-entry-name> ---> -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-type element contains the fully-qualified Java type of -the environment entry value that is expected by the application client's -code. - -The following are the legal values of env-entry-type: - - 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 - - -Used in: env-entry - -Example: - -<env-entry-type>java.lang.Boolean</env-entry-type> ---> -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The env-entry-value element contains the value of an application client'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. - -Used in: env-entry - -Example: - -<env-entry-value>100.00</env-entry-value> ---> -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The home element contains the fully-qualified name of the enterprise -bean's home interface. - -Used in: ejb-ref - -Example: - -<home>com.aardvark.payroll.PayrollHome</home> ---> -<!ELEMENT home (#PCDATA)> - -<!-- -The icon element contains small-icon and large-icon elements that -specify the file names for small and a large GIF or JPEG icon images -used to represent the parent element in a GUI tool. - -Used in: application-client ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -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 application client's -jar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The remote element contains the fully-qualified name of the enterprise -bean's remote interface. - -Used in: ejb-ref - -Example: - -<remote>com.wombat.empl.EmployeeService</remote> ---> -<!ELEMENT remote (#PCDATA)> - -<!-- -The res-auth element specifies whether the application client code signs -on programmatically to the resource manager, or whether the Container -will sign on to the resource manager on behalf of the application client. In the -latter case, the Container uses information that is supplied by the -Deployer. - -The value of this element must be one of the two following: - - <res-auth>Application</res-auth> - <res-auth>Container</res-auth> - -Used in: resource-ref ---> -<!ELEMENT res-auth (#PCDATA)> - -<!-- -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. - -Used in: resource-ref ---> -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-sharing-scope element specifies whether connections obtained -through the given resource manager connection factory reference can be -shared. The value of this element, if specified, must be one of the -two following: - - <res-sharing-scope>Shareable</res-sharing-scope> - <res-sharing-scope>Unshareable</res-sharing-scope> - -The default value is Shareable. - -Used in: resource-ref ---> -<!ELEMENT res-sharing-scope (#PCDATA)> - -<!-- -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. - -Used in: resource-ref ---> -<!ELEMENT res-type (#PCDATA)> - -<!-- -The resource-env-ref element contains a declaration of an application client's -reference to an administered object associated with a resource -in the application client's environment. It consists of an optional -description, the resource environment reference name, and an -indication of the resource environment reference type expected by -the application client code. - -Used in: application-client - -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> ---> -<!ELEMENT resource-env-ref (description?, resource-env-ref-name, - resource-env-ref-type)> - -<!-- -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. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-name (#PCDATA)> - -<!-- -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. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-type (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of an application client's -reference to an external resource. It consists of an optional -description, the resource manager connection factory reference name, -the indication of the resource manager connection factory type -expected by the application client code, the type of authentication -(Application or Container), and an optional specification of the -shareability of connections obtained from the resource (Shareable or -Unshareable). - -Used in: application-client - -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> ---> -<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth, - res-sharing-scope?)> - -<!-- -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 application client's -jar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e., information beyond the standard deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tool-specific files to the -information in the standard deployment descriptor. - -Tools are not allowed to add the non-standard information into the -standard deployment descriptor. ---> - -<!ATTLIST application-client id ID #IMPLIED> -<!ATTLIST callback-handler id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-sharing-scope id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST resource-env-ref id ID #IMPLIED> -<!ATTLIST resource-env-ref-name id ID #IMPLIED> -<!ATTLIST resource-env-ref-type id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_4.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_4.xsd deleted file mode 100644 index ec889717a5..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application-client_1_4.xsd +++ /dev/null @@ -1,267 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.4"> - <xsd:annotation> - <xsd:documentation> - @(#)application-client_1_4.xsds 1.17 02/11/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the application client 1.4 - 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 J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and indicate the version of the schema by - using the version element as shown below: - - <application-client xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd" - version="1.4"> - ... - </application-client> - - 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-client_1_4.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="application-client" type="j2ee: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="j2ee:env-entry"/> - <xsd:field xpath="j2ee: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="j2ee:ejb-ref"/> - <xsd:field xpath="j2ee: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="j2ee:resource-ref"/> - <xsd:field xpath="j2ee: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="j2ee:resource-env-ref"/> - <xsd:field xpath="j2ee: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="j2ee:message-destination-ref"/> - <xsd:field xpath="j2ee:message-destination-ref-name"/> - </xsd:unique> - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="application-clientType"> - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="env-entry" - type="j2ee:env-entryType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-ref" - type="j2ee:ejb-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:group ref="j2ee:service-refGroup"/> - <xsd:element name="resource-ref" - type="j2ee:resource-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="resource-env-ref" - type="j2ee:resource-env-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="message-destination-ref" - type="j2ee:message-destination-refType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="callback-handler" - type="j2ee: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="j2ee:message-destinationType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="1.4" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 1.4. - - </xsd:documentation> - </xsd:annotation> - - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - 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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_2.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_2.dtd deleted file mode 100644 index 67573627b2..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_2.dtd +++ /dev/null @@ -1,197 +0,0 @@ -<!-- -Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - - - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ -Copyright 1999 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - -<!-- -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. ---> -<!ELEMENT alt-dd (#PCDATA)> - -<!-- -The application element is the root element of a J2EE application deployment -descriptor. ---> -<!ELEMENT application (icon?, display-name, description?, module+, -security-role*)> - -<!-- -The context-root element specifies the context root of a web application ---> -<!ELEMENT context-root (#PCDATA)> - -<!-- -The description element provides a human readable description of the -application. The description element should include any information that the -application assembler wants to provide the deployer. ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element specifies an application name. -The application name is assigned to the application by the application assembler -and is used to identify the application to the deployer at deployment time. ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb element specifies the URI of a ejb-jar, relative to the top level of the -application package. ---> -<!ELEMENT ejb (#PCDATA)> - -<!-- -The icon element contains a small-icon and large-icon element which specify the -URIs for a small and a large GIF or JPEG icon image to represent the application -in a GUI. ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -The java element specifies the URI of a java application client module, relative -to the top level of the application package. ---> -<!ELEMENT java (#PCDATA)> - -<!-- -The large-icon element specifies the URI for a large GIF or JPEG icon image to -represent the application in a GUI. ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The module element represents a single J2EE module and contains an 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 application deployment descriptor must have one module element for each J2EE -module in the application package. ---> -<!ELEMENT module ((ejb | java | web), alt-dd?)> - -<!-- -The role-name element contains the name of a security role. ---> -<!ELEMENT role-name (#PCDATA)> - -<!-- -The security-role element contains the definition of a security role which is -global to the application. The definition consists of a description of the -security role, and the security role name. The descriptions at this level -override those in the component level security-role definitions and must be the -descriptions tool display to the deployer. ---> -<!ELEMENT security-role (description?, role-name)> - -<!-- -The small-icon element specifies the URI for a small GIF or JPEG icon image to -represent the application in a GUI. ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The web element contains the web-uri and context-root of a web application -module. ---> -<!ELEMENT web (web-uri, context-root)> - -<!-- -The web-uri element specifies the URI of a web application file, relative to the -top level of the application package. ---> -<!ELEMENT web-uri (#PCDATA)> - -<!-- -The ID mechanism is to allow tools to easily make tool-specific references to -the elements of the deployment descriptor. - --> -<!ATTLIST alt-dd id ID #IMPLIED> -<!ATTLIST application id ID #IMPLIED> -<!ATTLIST context-root id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST java id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST module id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST web id ID #IMPLIED> -<!ATTLIST web-uri id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_3.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_3.dtd deleted file mode 100644 index 22a49aca1e..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_3.dtd +++ /dev/null @@ -1,312 +0,0 @@ -<!-- -Copyright (c) 2000 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 embodied in the product that is 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 in other countries. - -This document and the product to which it pertains are distributed -under licenses restricting their use, copying, distribution, and -decompilation. This document may be reproduced and distributed but may -not be changed 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, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and and -Enterprise JavaBeans 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. - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED -WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR -NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH -DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. - - -_________________________________________________________________________ - -Copyright (c) 2000 Sun Microsystems, Inc., -901 San Antonio Road, -Palo Alto, California 94303, E'tats-Unis. -Tous droits re'serve's. - -Sun Microsystems, Inc. a les droits de proprie'te' intellectuels -relatants a` la technologie incorpore'e dans le produit qui est de'crit -dans ce document. En particulier, et sans la limitation, ces droits de -proprie'te' intellectuels peuvent inclure un ou plus des brevets -ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les -brevets plus supple'mentaires ou les applications de brevet en attente -dans les E'tats-Unis et dans les autres pays. - -Ce produit ou document est prote'ge' par un copyright et distribue' -avec des licences qui en restreignent l'utilisation, la copie, la -distribution, et la de'compilation. Ce documention associe n peut -e^tre reproduite et distribuer, par quelque moyen que ce soit, sans -l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de -licence, le cas e'che'ant. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright et -licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail et and -Enterprise JavaBeans sont des marques de fabrique ou des marques -de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres -pays. - -LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT -EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS -NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A -L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE -CONTREFAC,ON. ---> - -<!-- -This is the XML DTD for the J2EE 1.3 application deployment -descriptor. All J2EE 1.3 application deployment descriptors -must include a DOCTYPE of the following form: - - <!DOCTYPE application PUBLIC - "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" - "http://java.sun.com/dtd/application_1_3.dtd"> - ---> - -<!-- -The following conventions apply to all J2EE deployment descriptor -elements unless indicated otherwise. - -- In elements that contain PCDATA, leading and trailing whitespace - in the data may be ignored. - -- In elements whose value is an "enumerated type", the value is - case sensitive. - -- 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. ---> -<!ELEMENT application (icon?, display-name, description?, module+, - security-role*)> - -<!-- -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. - -Used in: module ---> -<!ELEMENT alt-dd (#PCDATA)> - -<!-- -The connector element specifies the URI of a resource adapter archive -file, relative to the top level of the application package. - -Used in: module ---> -<!ELEMENT connector (#PCDATA)> - -<!-- -The context-root element specifies the context root of a web -application. - -Used in: web ---> -<!ELEMENT context-root (#PCDATA)> - -<!-- -The description element is used to provide text describing the parent -element. The description element should include any information that -the application ear file producer wants to provide to the consumer of -the application ear file (i.e., to the Deployer). Typically, the tools -used by the application ear file consumer will display the description -when processing the parent element that contains the description. - -Used in: application, security-role ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -displayed by tools. The display name need not be unique. - -Used in: application - -Example: - -<display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb element specifies the URI of an ejb-jar, relative to the top -level of the application package. - -Used in: module ---> -<!ELEMENT ejb (#PCDATA)> - -<!-- -The icon element contains small-icon and large-icon elements that -specify the file names for small and a large GIF or JPEG icon images -used to represent the parent element in a GUI tool. - -Used in: application ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -The java element specifies the URI of a java application client module, -relative to the top level of the application package. - -Used in: module ---> -<!ELEMENT java (#PCDATA)> - -<!-- -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 application's -ear file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The module element represents 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 application deployment descriptor must have one module element for -each J2EE module in the application package. - -Used in: application ---> -<!ELEMENT module ((connector | ejb | java | web), alt-dd?)> - -<!-- -The role-name element contains the name of a security role. - -The name must conform to the lexical rules for an NMTOKEN. - -Used in: security-role ---> -<!ELEMENT role-name (#PCDATA)> - -<!-- -The security-role element contains the definition of a security -role. The definition consists of an optional description of the -security role, and the security role name. - -Used in: application - -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> ---> -<!ELEMENT security-role (description?, role-name)> - -<!-- -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 application's -ear file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The web element contains the web-uri and context-root of a web -application module. - -Used in: module ---> -<!ELEMENT web (web-uri, context-root)> - -<!-- -The web-uri element specifies the URI of a web application file, -relative to the top level of the application package. - -Used in: web ---> -<!ELEMENT web-uri (#PCDATA)> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e., information beyond the standard deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tool-specific files to the -information in the standard deployment descriptor. - -Tools are not allowed to add the non-standard information into the -standard deployment descriptor. ---> - -<!ATTLIST alt-dd id ID #IMPLIED> -<!ATTLIST application id ID #IMPLIED> -<!ATTLIST connector id ID #IMPLIED> -<!ATTLIST context-root id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST java id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST module id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST web id ID #IMPLIED> -<!ATTLIST web-uri id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_4.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_4.xsd deleted file mode 100644 index c458cfd5dd..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_1_4.xsd +++ /dev/null @@ -1,315 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.4"> - <xsd:annotation> - <xsd:documentation> - @(#)application_1_4.xsds 1.13 02/11/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the application 1.4 deployment - descriptor. The deployment descriptor must be named - "META-INF/application.xml" in the application's ear file. - All application deployment descriptors must indicate - the application schema by using the J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and indicate the version of the schema by - using the version element as shown below: - - <application xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" - version="1.4"> - ... - </application> - - 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 - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="application" type="j2ee:applicationType"> - <xsd:annotation> - <xsd:documentation> - - The application element is the root element of a J2EE - application deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - - <xsd:unique name="context-root-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The context-root element content must be unique - in the ear. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:module/j2ee:web"/> - <xsd:field xpath="j2ee:context-root"/> - </xsd:unique> - - <xsd:unique name="security-role-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The security-role-name element content - must be unique in the ear. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:security-role"/> - <xsd:field xpath="j2ee:role-name"/> - </xsd:unique> - - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="applicationType"> - <xsd:annotation> - <xsd:documentation> - - The applicationType defines the structure of the - application. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="module" - type="j2ee:moduleType" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="security-role" - type="j2ee:security-roleType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="1.4" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 1.4. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="moduleType"> - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:choice> - <xsd:element name="connector" - type="j2ee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The connector element specifies the URI of a - resource adapter archive file, relative to the - top level of the application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb" - type="j2ee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The ejb element specifies the URI of an ejb-jar, - relative to the top level of the application - package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="java" - type="j2ee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The java element specifies the URI of a java - application client module, relative to the top - level of the application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="web" - type="j2ee:webType"/> - </xsd:choice> - <xsd:element name="alt-dd" - type="j2ee:pathType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webType"> - <xsd:annotation> - <xsd:documentation> - - The webType defines the web-uri and context-root of - a web application module. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="web-uri" - type="j2ee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The web-uri element specifies the URI of a web - application file, relative to the top level of the - application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="context-root" - type="j2ee:string"> - - <xsd:annotation> - <xsd:documentation> - - The context-root element specifies the context root - of a web application. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_5.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_5.xsd deleted file mode 100644 index 4509662086..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/application_5.xsd +++ /dev/null @@ -1,336 +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_5.xsds 1.17 08/05/05 - </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 5 deployment - descriptor. The deployment descriptor must be named - "META-INF/application.xml" in the application's ear file. - All application deployment descriptors must indicate - the application 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 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_5.xsd" - version="5"> - ... - </application> - - 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_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" type="javaee:applicationType"> - <xsd:annotation> - <xsd:documentation> - - The application element is the root element of a Java EE - application deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - - <xsd:unique name="context-root-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The context-root element content must be unique - in the ear. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:module/javaee:web"/> - <xsd:field xpath="javaee:context-root"/> - </xsd:unique> - - <xsd:unique name="security-role-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The security-role-name element content - must be unique in the ear. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:security-role"/> - <xsd:field xpath="javaee:role-name"/> - </xsd:unique> - - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="applicationType"> - <xsd:annotation> - <xsd:documentation> - - The applicationType defines the structure of the - application. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="module" - type="javaee:moduleType" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The application deployment descriptor must have one - module element for each Java EE module in the - application package. A module element is defined - by moduleType definition. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="security-role" - type="javaee:security-roleType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="library-directory" - type="javaee:pathType" - minOccurs="0" - maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The library-directory element specifies the pathname - of a directory within the application package, relative - to the top level of the application package. All files - named "*.jar" in this directory must be made available - in the class path of all components included in this - application package. If this element isn't specified, - the directory named "lib" is searched. An empty element - may be used to disable searching. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </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="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="moduleType"> - <xsd:annotation> - <xsd:documentation> - - The moduleType defines a single Java EE 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:choice> - <xsd:element name="connector" - type="javaee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The connector element specifies the URI of a - resource adapter archive file, relative to the - top level of the application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb" - type="javaee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The ejb element specifies the URI of an ejb-jar, - relative to the top level of the application - package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="java" - type="javaee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The java element specifies the URI of a java - application client module, relative to the top - level of the application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="web" - type="javaee:webType"/> - </xsd:choice> - <xsd:element name="alt-dd" - type="javaee:pathType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The alt-dd element specifies an optional URI to the - post-assembly version of the deployment descriptor - file for a particular Java EE 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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webType"> - <xsd:annotation> - <xsd:documentation> - - The webType defines the web-uri and context-root of - a web application module. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="web-uri" - type="javaee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The web-uri element specifies the URI of a web - application file, relative to the top level of the - application package. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="context-root" - type="javaee:string"> - - <xsd:annotation> - <xsd:documentation> - - The context-root element specifies the context root - of a web application. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_0.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_0.dtd deleted file mode 100644 index 1ab3b55a0d..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_0.dtd +++ /dev/null @@ -1,557 +0,0 @@ -<!-- -Copyright 2000-2001 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ - -Copyright 2000-2001 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - -<!-- -This is the XML DTD for the Connector 1.0 deployment descriptor. -All Connector 1.0 deployment descriptors must include a DOCTYPE -of the following form: - - <!DOCTYPE connector PUBLIC - "-//Sun Microsystems, Inc.//DTD Connector 1.0//EN" - "http://java.sun.com/dtd/connector_1_0.dtd"> - ---> - -<!-- -The following conventions apply to all J2EE deployment descriptor -elements unless indicated otherwise. - -- In elements that contain PCDATA, leading and trailing whitespace - in the data may be ignored. - -- In elements whose value is an "enumerated type", the value is - case sensitive. - -- 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 connector element is the root element of the deployment descriptor -for the resource adapter. This element includes general information - vendor -name, version, specification version supported, icon - about the -resource adapter module. It also includes information specific to the -implementation of the resource adapter library as specified through -the element resourceadapter. ---> -<!ELEMENT connector (display-name?, description?, icon?, vendor-name, -spec-version, eis-type, version, license?, resourceadapter)> - -<!-- -The element authentication-mechanism specifies an authentication mechanism -supported by the resource adapter. Note that this support is for -the resource adapter and not for the underlying EIS instance. The -optional description specifies any resource adapter specific requirement -for the support of security contract and authentication mechanism. - -Note that BasicPassword mechanism type should support the -javax.resource.spi.security.PasswordCredential interface. -The Kerbv5 mechanism type should support the -javax.resource.spi.security.GenericCredential interface. - -Used in: resourceadapter ---> -<!ELEMENT authentication-mechanism ( -description?, authentication-mechanism-type, credential-interface)> - -<!-- -The element authentication-mechanism-type specifies type of an authentication -mechanism. - -The example values are: - <authentication-mechanism-type>BasicPassword - </authentication-mechanism-type> - <authentication-mechanism-type>Kerbv5 - </authentication-mechanism-type> - -Any additional security mechanisms are outside the scope of the -Connector architecture specification. - -Used in: authentication-mechanism ---> -<!ELEMENT authentication-mechanism-type (#PCDATA)> - -<!-- -The element config-property contains a declaration of a single -configuration property for a ManagedConnectionFactory instance. - -Each ManagedConnectionFactory instance creates connections to a -specific EIS instance based on the properties configured on the -ManagedConnectionFactory instance. The configurable properties are -specified only once in the deployment descriptor, even though a -resource adapter can be used to configure multiple ManagedConnnection- -Factory instances (that create connections to different instances of -the same EIS). - -The declaration consists of an optional description, name, type -and an optional value of the configuration property. If the resource -adapter provider does not specify a value than the deployer is -responsible for providing a valid value for a configuration property. - -Any bounds or well-defined values of properties should be described -in the description element. - -Used in: resourceadapter ---> -<!ELEMENT config-property (description?, config-property-name, -config-property-type, config-property-value?)> - -<!-- -The element config-property-name contains the name of a configuration -property. - -The connector architecture defines a set of well-defined properties -all of type java.lang.String. These are as follows: - <config-property-name>ServerName</config-property-name> - <config-property-name>PortNumber</config-property-name> - <config-property-name>UserName</config-property-name> - <config-property-name>Password</config-property-name> - <config-property-name>ConnectionURL</config-property-name> - -A resource adapter provider can extend this property set to include -properties specific to the resource adapter and its underlying EIS. - -Used in: config-property - -Example: <config-property-name>ServerName</config-property-name> ---> -<!ELEMENT config-property-name (#PCDATA)> - -<!-- -The element config-property-type contains the fully qualified Java -type of a configuration property as required by ManagedConnection- -Factory instance. - -The following are the legal values of config-property-type: - java.lang.Boolean, java.lang.String, java.lang.Integer, - java.lang.Double, java.lang.Byte, java.lang.Short, - java.lang.Long, java.lang.Float, java.lang.Character - -Used in: config-property - -Example: <config-property-type>java.lang.String</config-property-type> ---> -<!ELEMENT config-property-type (#PCDATA)> - -<!-- -The element config-property-value contains the value of a configuration -entry. - -Used in: config-property - -Example: <config-property-value>WombatServer</config-property-value> ---> -<!ELEMENT config-property-value (#PCDATA)> - -<!-- -The element connection-impl-class specifies the fully-qualified -name of the Connection class that implements resource adapter -specific Connection interface. - -Used in: resourceadapter - -Example: <connection-impl-class>com.wombat.ConnectionImpl - </connection-impl-class> ---> -<!ELEMENT connection-impl-class (#PCDATA)> - -<!-- -The element connection-interface specifies the fully-qualified -name of the Connection interface supported by the resource -adapter. - -Used in: resourceadapter - -Example: <connection-interface>javax.resource.cci.Connection - </connection-interface> ---> -<!ELEMENT connection-interface (#PCDATA)> - -<!-- -The element connectionfactory-impl-class specifies the fully-qualified -name of the ConnectionFactory class that implements resource adapter -specific ConnectionFactory interface. - -Used in: resourceadapter - -Example: <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl - </connectionfactory-impl-class> ---> -<!ELEMENT connectionfactory-impl-class (#PCDATA)> - -<!-- -The element connectionfactory-interface specifies the fully-qualified -name of the ConnectionFactory interface supported by the resource -adapter. - -Used in: resourceadapter - -Example: <connectionfactory-interface>com.wombat.ConnectionFactory - </connectionfactory-interface> -OR -<connectionfactory-interface>javax.resource.cci.ConnectionFactory - </connectionfactory-interface> ---> -<!ELEMENT connectionfactory-interface (#PCDATA)> - -<!-- -The element credential-interface specifies the interface that the -resource adapter implementation supports for the representation -of the credentials. This element should be used by application server -to find out the Credential interface it should use as part of the -security contract. - -The possible values are: - <credential-interface>javax.resource.spi.security.PasswordCredential - </credential-interface> - <credential-interface>javax.resource.spi.security.GenericCredential - </credential-interface> - -Used in: authentication-mechanism ---> -<!ELEMENT credential-interface (#PCDATA)> - -<!-- -The description element is used to provide text describing the parent -element. The description element should include any information that -the resource adapter rar file producer wants to provide to the consumer of -the resource adapter rar file (i.e., to the Deployer). Typically, the tools -used by the resource adapter rar file consumer will display the description -when processing the parent element that contains the description. - -Used in: authentication-mechanism, config-property, connector, license, -security-permission ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -displayed by tools. The display name need not be unique. - -Used in: connector - -Example: - -<display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The element eis-type contains information about the type of the -EIS. For example, the type of an EIS can be product name of EIS -independent of any version info. - -This helps in identifying EIS instances that can be used with -this resource adapter. - -Used in: connector ---> -<!ELEMENT eis-type (#PCDATA)> - -<!-- -The icon element contains small-icon and large-icon elements that -specify the file names for small and a large GIF or JPEG icon images -used to represent the parent element in a GUI tool. - -Used in: connector ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -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 resource adapter's -rar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The element license specifies licensing requirements for the resource -adapter module. This element specifies whether a license is required -to deploy and use this resource adapter, and an optional description -of the licensing terms (examples: duration of license, number of -connection restrictions). - -Used in: connector ---> -<!ELEMENT license (description?, license-required)> - -<!-- -The element license-required specifies whether a license is required -to deploy and use the resource adapter. This element must be one of -the following: - - <license-required>true</license-required> - <license-required>false</license-required> - -Used in: license ---> -<!ELEMENT license-required (#PCDATA)> - -<!-- -The element managedconnectionfactory-class specifies the fully qualified -name of the Java class that implements the javax.resource.spi.Managed- -ConnectionFactory interface. This Java class is provided as part of -resource adapter's implementation of connector architecture specified -contracts. - -Used in: resourceadapter - -Example: - <managedconnectionfactory-class>com.wombat.ManagedConnectionFactoryImpl - </managedconnectionfactory-class> ---> -<!ELEMENT managedconnectionfactory-class (#PCDATA)> - -<!-- -The element reauthentication-support specifies whether the resource -adapter implementation supports re-authentication of existing Managed- -Connection instance. Note that this information is for the resource -adapter implementation and not for the underlying EIS instance. - -This element must be one of the following: - <reauthentication-support>true</reauthentication-support> - <reauthentication-support>false</reauthentication-support> -Used in: resourceadapter ---> -<!ELEMENT reauthentication-support (#PCDATA)> - -<!-- -The element resourceadapter specifies information about the resource -adapter. The information includes fully-qualified names of -class/interfaces required as part of the connector architecture -specified contracts, level of transaction support provided, -configurable properties for ManagedConnectionFactory instances, -one or more authentication mechanisms supported and additional -required security permissions. - -If there is no authentication-mechanism specified as part of -resource adapter element then the resource adapter does not -support any standard security authentication mechanisms as part -of security contract. The application server ignores the security -part of the system contracts in this case. - -Used in: connector ---> -<!ELEMENT resourceadapter ( -managedconnectionfactory-class, connectionfactory-interface, -connectionfactory-impl-class, connection-interface, -connection-impl-class, transaction-support, config-property*, -authentication-mechanism*, reauthentication-support, security-permission* -)> - -<!-- -The element security permission specifies a security permission that -is required by the resource adapter code. - -The security permission listed in the deployment descriptor are ones -that are different from those required by the default permission set -as specified in the connector specification. The optional description -can mention specific reason that resource adapter requires a given -security permission. - -Used in: resourceadapter ---> -<!ELEMENT security-permission (description?, security-permission-spec)> - -<!-- -The element permission-spec specifies a security permission based -on the Security policy file syntax. Refer to the following URL for -Sun's implementation of the security permission specification: - -http: - -Used in: security-permission ---> -<!ELEMENT security-permission-spec (#PCDATA)> - -<!-- -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 resource adapter's -rar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The element spec-version specifies the version of the connector -architecture specification that is supported by this resource -adapter. This information enables deployer to configure the resource -adapter to support deployment and runtime requirements of the -corresponding connector architecture specification. - -Used in: connector - -Example: - <spec-version>1.0</spec-version> ---> -<!ELEMENT spec-version (#PCDATA)> - -<!-- -The transaction-support element specifies the level of transaction -support provided by the resource adapter. -The value of transaction-support must be one of the following: - <transaction-support>NoTransaction</transaction-support> - <transaction-support>LocalTransaction</transaction-support> - <transaction-support>XATransaction</transaction-support> - -Used in: resourceadapter ---> -<!ELEMENT transaction-support (#PCDATA)> - -<!-- -The element vendor-name specifies the name of resource adapter provider -vendor. - -Used in: connector - -Example: - <vendor-name>Wombat Corp.</vendor-name> ---> -<!ELEMENT vendor-name (#PCDATA)> - -<!-- -The element version specifies a string-based version of the -resource adapter from the resource adapter provider. - -Used in: connector - -Example: - <version>1.0</version> ---> -<!ELEMENT version (#PCDATA)> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e., information beyond the standard deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tool-specific files to the -information in the standard deployment descriptor. - -Tools are not allowed to add the non-standard information into the -standard deployment descriptor. ---> - -<!ATTLIST authentication-mechanism id ID #IMPLIED> -<!ATTLIST authentication-mechanism-type id ID #IMPLIED> -<!ATTLIST config-property id ID #IMPLIED> -<!ATTLIST config-property-name id ID #IMPLIED> -<!ATTLIST config-property-type id ID #IMPLIED> -<!ATTLIST config-property-value id ID #IMPLIED> -<!ATTLIST connection-impl-class id ID #IMPLIED> -<!ATTLIST connection-interface id ID #IMPLIED> -<!ATTLIST connectionfactory-impl-class id ID #IMPLIED> -<!ATTLIST connectionfactory-interface id ID #IMPLIED> -<!ATTLIST connector id ID #IMPLIED> -<!ATTLIST credential-interface id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST eis-type id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST license id ID #IMPLIED> -<!ATTLIST license-required id ID #IMPLIED> -<!ATTLIST managedconnectionfactory-class id ID #IMPLIED> -<!ATTLIST reauthentication-support id ID #IMPLIED> -<!ATTLIST resourceadapter id ID #IMPLIED> -<!ATTLIST security-permission id ID #IMPLIED> -<!ATTLIST security-permission-spec id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST spec-version id ID #IMPLIED> -<!ATTLIST transaction-support id ID #IMPLIED> -<!ATTLIST vendor-name id ID #IMPLIED> -<!ATTLIST version id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_5.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_5.xsd deleted file mode 100644 index 26d19129c4..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/connector_1_5.xsd +++ /dev/null @@ -1,1036 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.5"> - <xsd:annotation> - <xsd:documentation> - @(#)connector_1_5.xsds 1.27 06/17/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the Connector 1.5 deployment - descriptor. The deployment descriptor must be named - "META-INF/ra.xml" in the connector's rar file. All Connector - deployment descriptors must indicate the connector resource - adapter schema by using the J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and by indicating the version of the schema by - using the version element as shown below: - - <connector xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd" - version="1.5"> - ... - </connector> - - 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/connector_1_5.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="connector" type="j2ee:connectorType"> - <xsd:annotation> - <xsd:documentation> - - The connector element is the root element of the deployment - descriptor for the resource adapter. This element includes - general information - vendor name, resource adapter version, - icon - about the resource adapter module. It also includes - information specific to the implementation of the resource - adapter library as specified through the element - resourceadapter. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="activationspecType"> - <xsd:annotation> - <xsd:documentation> - - The activationspecType specifies an activation - specification. The information includes fully qualified - Java class name of an activation specification and a set of - required configuration property names. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="activationspec-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element activationspec-class specifies the fully - qualified Java class name of the activation - specification class. This class must implement the - javax.resource.spi.ActivationSpec interface. The - implementation of this class is required to be a - JavaBean. - - Example: - <activationspec-class>com.wombat.ActivationSpecImpl - </activationspec-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="required-config-property" - type="j2ee:required-config-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="adminobjectType"> - <xsd:annotation> - <xsd:documentation> - - The adminobjectType specifies information about an - administered object. Administered objects are specific to a - messaging style or message provider. This contains - information on the Java type of the interface implemented by - an administered object, its Java class name and its - configuration properties. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="adminobject-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element adminobject-interface specifies the - fully qualified name of the Java type of the - interface implemented by an administered object. - - Example: - <adminobject-interface>javax.jms.Destination - </adminobject-interface> - - ]]> - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="adminobject-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element adminobject-class specifies the fully - qualified Java class name of an administered object. - - Example: - <adminobject-class>com.wombat.DestinationImpl - </adminobject-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="config-property" - type="j2ee:config-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="authentication-mechanismType"> - <xsd:annotation> - <xsd:documentation> - - The authentication-mechanismType specifies an authentication - mechanism supported by the resource adapter. Note that this - support is for the resource adapter and not for the - underlying EIS instance. The optional description specifies - any resource adapter specific requirement for the support of - security contract and authentication mechanism. - - Note that BasicPassword mechanism type should support the - javax.resource.spi.security.PasswordCredential interface. - The Kerbv5 mechanism type should support the - org.ietf.jgss.GSSCredential interface or the deprecated - javax.resource.spi.security.GenericCredential interface. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="authentication-mechanism-type" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element authentication-mechanism-type specifies - type of an authentication mechanism. - - The example values are: - - <authentication-mechanism-type>BasicPassword - </authentication-mechanism-type> - - <authentication-mechanism-type>Kerbv5 - </authentication-mechanism-type> - - Any additional security mechanisms are outside the - scope of the Connector architecture specification. - - ]]> - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="credential-interface" - type="j2ee:credential-interfaceType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="config-property-nameType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The config-property-nameType contains the name of a - configuration property. - - The connector architecture defines a set of well-defined - properties all of type java.lang.String. These are as - follows. - - ServerName - PortNumber - UserName - Password - ConnectionURL - - A resource adapter provider can extend this property set to - include properties specific to the resource adapter and its - underlying EIS. - - Possible values include - ServerName - PortNumber - UserName - Password - ConnectionURL - - Example: <config-property-name>ServerName</config-property-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:xsdStringType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="config-property-typeType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The config-property-typeType contains the fully - qualified Java type of a configuration property. - - The following are the legal values: - java.lang.Boolean, java.lang.String, java.lang.Integer, - java.lang.Double, java.lang.Byte, java.lang.Short, - java.lang.Long, java.lang.Float, java.lang.Character - - Used in: config-property - - Example: - <config-property-type>java.lang.String</config-property-type> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="java.lang.Boolean"/> - <xsd:enumeration value="java.lang.String"/> - <xsd:enumeration value="java.lang.Integer"/> - <xsd:enumeration value="java.lang.Double"/> - <xsd:enumeration value="java.lang.Byte"/> - <xsd:enumeration value="java.lang.Short"/> - <xsd:enumeration value="java.lang.Long"/> - <xsd:enumeration value="java.lang.Float"/> - <xsd:enumeration value="java.lang.Character"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="config-propertyType"> - <xsd:annotation> - <xsd:documentation> - - The config-propertyType contains a declaration of a single - configuration property that may be used for providing - configuration information. - - The declaration consists of an optional description, name, - type and an optional value of the configuration property. If - the resource adapter provider does not specify a value than - the deployer is responsible for providing a valid value for - a configuration property. - - Any bounds or well-defined values of properties should be - described in the description element. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="config-property-name" - type="j2ee:config-property-nameType"/> - <xsd:element name="config-property-type" - type="j2ee:config-property-typeType"/> - <xsd:element name="config-property-value" - type="j2ee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element config-property-value contains the value - of a configuration entry. Note, it is possible for a - resource adapter deployer to override this - configuration information during deployment. - - Example: - <config-property-value>WombatServer</config-property-value> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="connection-definitionType"> - <xsd:annotation> - <xsd:documentation> - - The connection-definitionType defines a set of connection - interfaces and classes pertaining to a particular connection - type. This also includes configurable properties for - ManagedConnectionFactory instances that may be produced out - of this set. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="managedconnectionfactory-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element managedconnectionfactory-class specifies - the fully qualified name of the Java class that - implements the - javax.resource.spi.ManagedConnectionFactory interface. - This Java class is provided as part of resource - adapter's implementation of connector architecture - specified contracts. The implementation of this - class is required to be a JavaBean. - - Example: - <managedconnectionfactory-class> - com.wombat.ManagedConnectionFactoryImpl - </managedconnectionfactory-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="config-property" - type="j2ee:config-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="connectionfactory-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element connectionfactory-interface specifies - the fully qualified name of the ConnectionFactory - interface supported by the resource adapter. - - Example: - <connectionfactory-interface>com.wombat.ConnectionFactory - </connectionfactory-interface> - - OR - - <connectionfactory-interface>javax.resource.cci.ConnectionFactory - </connectionfactory-interface> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="connectionfactory-impl-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element connectionfactory-impl-class specifies - the fully qualified name of the ConnectionFactory - class that implements resource adapter - specific ConnectionFactory interface. - - Example: - - <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl - </connectionfactory-impl-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="connection-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The connection-interface element specifies the fully - qualified name of the Connection interface supported - by the resource adapter. - - Example: - - <connection-interface>javax.resource.cci.Connection - </connection-interface> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="connection-impl-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The connection-impl-classType specifies the fully - qualified name of the Connection class that - implements resource adapter specific Connection - interface. It is used by the connection-impl-class - elements. - - Example: - - <connection-impl-class>com.wombat.ConnectionImpl - </connection-impl-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="connectorType"> - <xsd:annotation> - <xsd:documentation> - - The connectorType defines a resource adapter. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="vendor-name" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The element vendor-name specifies the name of - resource adapter provider vendor. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="eis-type" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The element eis-type contains information about the - type of the EIS. For example, the type of an EIS can - be product name of EIS independent of any version - info. - - This helps in identifying EIS instances that can be - used with this resource adapter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="resourceadapter-version" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The element resourceadapter-version specifies a string-based version - of the resource adapter from the resource adapter - provider. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="license" - type="j2ee:licenseType" - minOccurs="0"/> - <xsd:element name="resourceadapter" - type="j2ee:resourceadapterType"/> - - </xsd:sequence> - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="1.5" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The version specifies the version of the - connector architecture specification that is - supported by this resource adapter. This information - enables deployer to configure the resource adapter to - support deployment and runtime requirements of the - corresponding connector architecture specification. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="credential-interfaceType"> - <xsd:annotation> - <xsd:documentation> - - The credential-interfaceType specifies the - interface that the resource adapter implementation - supports for the representation of the - credentials. This element(s) that use this type, - i.e. credential-interface, should be used by - application server to find out the Credential - interface it should use as part of the security - contract. - - The possible values are: - - javax.resource.spi.security.PasswordCredential - org.ietf.jgss.GSSCredential - javax.resource.spi.security.GenericCredential - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:fully-qualified-classType"> - <xsd:enumeration - value="javax.resource.spi.security.PasswordCredential"/> - <xsd:enumeration - value="org.ietf.jgss.GSSCredential"/> - <xsd:enumeration - value="javax.resource.spi.security.GenericCredential"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="inbound-resourceadapterType"> - <xsd:annotation> - <xsd:documentation> - - The inbound-resourceadapterType specifies information - about an inbound resource adapter. This contains information - specific to the implementation of the resource adapter - library as specified through the messageadapter element. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="messageadapter" - type="j2ee:messageadapterType" - minOccurs="0"> - <xsd:unique name="messagelistener-type-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The messagelistener-type element content must be - unique in the messageadapter. Several messagelisteners - can not use the same messagelistener-type. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:messagelistener"/> - <xsd:field xpath="j2ee:messagelistener-type"/> - </xsd:unique> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="licenseType"> - <xsd:annotation> - <xsd:documentation> - - The licenseType specifies licensing requirements for the - resource adapter module. This type specifies whether a - license is required to deploy and use this resource adapter, - and an optional description of the licensing terms - (examples: duration of license, number of connection - restrictions). It is used by the license element. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="license-required" - type="j2ee:true-falseType"> - <xsd:annotation> - <xsd:documentation> - - The element license-required specifies whether a - license is required to deploy and use the - resource adapter. This element must be one of - the following, "true" or "false". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="messageadapterType"> - <xsd:annotation> - <xsd:documentation> - - The messageadapterType specifies information about the - messaging capabilities of the resource adapter. This - contains information specific to the implementation of the - resource adapter library as specified through the - messagelistener element. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="messagelistener" - type="j2ee:messagelistenerType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="messagelistenerType"> - <xsd:annotation> - <xsd:documentation> - - The messagelistenerType specifies information about a - specific message listener supported by the messaging - resource adapter. It contains information on the Java type - of the message listener interface and an activation - specification. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="messagelistener-type" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element messagelistener-type specifies the fully - qualified name of the Java type of a message - listener interface. - - Example: - - <messagelistener-type>javax.jms.MessageListener - </messagelistener-type> - - ]]> - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="activationspec" - type="j2ee:activationspecType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="outbound-resourceadapterType"> - <xsd:annotation> - <xsd:documentation> - - The outbound-resourceadapterType specifies information about - an outbound resource adapter. The information includes fully - qualified names of classes/interfaces required as part of - the connector architecture specified contracts for - connection management, level of transaction support - provided, one or more authentication mechanisms supported - and additional required security permissions. - - If there is no authentication-mechanism specified as part of - resource adapter element then the resource adapter does not - support any standard security authentication mechanisms as - part of security contract. The application server ignores - the security part of the system contracts in this case. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="connection-definition" - type="j2ee:connection-definitionType" - maxOccurs="unbounded"/> - <xsd:element name="transaction-support" - type="j2ee:transaction-supportType"/> - <xsd:element name="authentication-mechanism" - type="j2ee:authentication-mechanismType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="reauthentication-support" - type="j2ee:true-falseType"> - <xsd:annotation> - <xsd:documentation> - - The element reauthentication-support specifies - whether the resource adapter implementation supports - re-authentication of existing Managed- Connection - instance. Note that this information is for the - resource adapter implementation and not for the - underlying EIS instance. This element must have - either a "true" or "false" value. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="required-config-propertyType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The required-config-propertyType contains a declaration - of a single configuration property used for specifying a - required configuration property name. It is used - by required-config-property elements. - - Example: - - <required-config-property>Destination</required-config-property> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="config-property-name" - type="j2ee:config-property-nameType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="resourceadapterType"> - <xsd:annotation> - <xsd:documentation> - - The resourceadapterType specifies information about the - resource adapter. The information includes fully qualified - resource adapter Java class name, configuration properties, - information specific to the implementation of the resource - adapter library as specified through the - outbound-resourceadapter and inbound-resourceadapter - elements, and an optional set of administered objects. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="resourceadapter-class" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The element resourceadapter-class specifies the - fully qualified name of a Java class that implements - the javax.resource.spi.ResourceAdapter - interface. This Java class is provided as part of - resource adapter's implementation of connector - architecture specified contracts. The implementation - of this class is required to be a JavaBean. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="config-property" - type="j2ee:config-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="outbound-resourceadapter" - type="j2ee:outbound-resourceadapterType" - minOccurs="0"> - <xsd:unique name="connectionfactory-interface-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The connectionfactory-interface element content - must be unique in the outbound-resourceadapter. - Multiple connection-definitions can not use the - same connectionfactory-type. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:connection-definition"/> - <xsd:field xpath="j2ee:connectionfactory-interface"/> - </xsd:unique> - </xsd:element> - <xsd:element name="inbound-resourceadapter" - type="j2ee:inbound-resourceadapterType" - minOccurs="0"/> - <xsd:element name="adminobject" - type="j2ee:adminobjectType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="security-permission" - type="j2ee:security-permissionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-permissionType"> - <xsd:annotation> - <xsd:documentation> - - The security-permissionType specifies a security - permission that is required by the resource adapter code. - - The security permission listed in the deployment descriptor - are ones that are different from those required by the - default permission set as specified in the connector - specification. The optional description can mention specific - reason that resource adapter requires a given security - permission. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="security-permission-spec" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The element security-permission-spec specifies a security - permission based on the Security policy file - syntax. Refer to the following URL for Sun's - implementation of the security permission - specification: - - http://java.sun.com/products/jdk/1.4/docs/guide/security/PolicyFiles.html#FileSyntax - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="transaction-supportType"> - <xsd:annotation> - <xsd:documentation> - - The transaction-supportType specifies the level of - transaction support provided by the resource adapter. It is - used by transaction-support elements. - - The value must be one of the following: - - NoTransaction - LocalTransaction - XATransaction - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="NoTransaction"/> - <xsd:enumeration value="LocalTransaction"/> - <xsd:enumeration value="XATransaction"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_1_1.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_1_1.dtd deleted file mode 100644 index efd838ee0b..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_1_1.dtd +++ /dev/null @@ -1,894 +0,0 @@ -<!-- -Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - - - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ -Copyright 1999 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - - -<!-- -This is the XML DTD for the EJB 1.1 deployment descriptor. ---> - - -<!-- -The assembly-descriptor element contains application-assembly information. - -The application-assembly information consists of the following parts: -the definition of security roles, the definition of method permissions, -and the definition of transaction attributes for enterprise beans with -container-managed transaction demarcation. - -All the parts are optional in the sense that they are omitted if the -lists represented by them are empty. - -Providing an assembly-descriptor in the deployment descriptor is -optional for the ejb-jar file producer. - -Used in: ejb-jar ---> -<!ELEMENT assembly-descriptor (security-role*, method-permission*, - container-transaction*)> - -<!-- -The cmp-field element describes a container-managed field. The field -element includes an optional description of the field, and the name of -the field. - -Used in: entity ---> -<!ELEMENT cmp-field (description?, field-name)> - -<!-- -The container-transaction element specifies how the container must -manage transaction scopes for the enterprise bean's method invocations. -The element consists of an optional description, a list of method -elements, and a transaction attribute.The transaction attribute is to -be applied to all the specified methods. - -Used in: assembly-descriptor ---> -<!ELEMENT container-transaction (description?, method+, - trans-attribute)> - -<!-- -The description element is used by the ejb-jar file producer to provide -text describing the parent element. - -The description element should include any information that the ejb-jar -file producer wants to provide to the consumer of the ejb-jar file -(i.e. to the Deployer). Typically, the tools used by the ejb-jar file -consumer will display the description when processing the parent -element. - -Used in: cmp-field, container-transaction, ejb-jar, entity, env-entry, -ejb-ref, method, method-permission, resource-ref, security-role, -security-role-ref, and session. ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -display by tools. - -Used in: ejb-jar, session, and entity - -Example: - <display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb-class element contains the fully-qualified name of the -enterprise bean's class. - -Used in: entity and session - -Example: - <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class> ---> -<!ELEMENT ejb-class (#PCDATA)> - -<!-- -The optional ejb-client-jar element specifies a JAR file that contains -the class files necessary for a client program to access the enterprise -beans in the ejb-jar file. The Deployer should make the ejb-client JAR -file accessible to the client's class-loader. - -Used in: ejb-jar - -Example: - <ejb-client-jar>employee_service_client.jar</ejb-client-jar> ---> -<!ELEMENT ejb-client-jar (#PCDATA)> - -<!-- -The ejb-jar element is the root element of the EJB deployment -descriptor. It contains an optional description of the ejb-jar file, -optional display name, optional small icon file name, optional large -icon file name, mandatory structural information about all included -enterprise beans, optional application-assembly descriptor, and an -optional name of an ejb-client-jar file for the ejb-jar. ---> -<!ELEMENT ejb-jar (description?, display-name?, small-icon?, - large-icon?, enterprise-beans, assembly-descriptor?, - ejb-client-jar?)> - -<!-- -The ejb-link element is used in the ejb-ref element to specify that an -EJB reference is linked to another enterprise bean in the ejb-jar -file. - -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 -J2EE application unit. - -Used in: ejb-ref - -Example: - <ejb-link>EmployeeRecord</ejb-link> ---> -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ejb-name element specifies an enterprise bean's name. This name is -assigned by the ejb-jar file producer to name the enterprise bean in -the ejb-jar file's deployment descriptor. The name must be unique among -the names of the enterprise beans in the same ejb-jar file. - -The enterprise bean code does not depend on the name; therefore the -name can be changed during the application-assembly process without -breaking the enterprise bean's function. - -There is no architected relationship between the ejb-name in the -deployment descriptor and the JNDI name that the Deployer will assign -to the enterprise bean's home. - -The name must conform to the lexical rules for an NMTOKEN. - -Used in: entity, method, and session - -Example: - <ejb-name>EmployeeService</ejb-name> ---> -<!ELEMENT ejb-name (#PCDATA)> - -<!-- -The ejb-ref element is used for the declaration of a reference to -another enterprise bean's home. The declaration consists of an optional -description; the EJB reference name used in the code of the referencing -enterprise bean; the expected type of the referenced enterprise bean; -the expected home and remote interfaces of the referenced enterprise -bean; and an optional ejb-link information. - -The optional ejb-link element is used to specify the referenced -enterprise bean. It is used typically in ejb-jar files that contain an -assembled application. - -Used in: entity and session ---> -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, - remote, ejb-link?)> - -<!-- -The ejb-ref-name element contains the name of an EJB reference. The EJB -reference is an entry in the enterprise bean's environment. - -It is recommended that name is prefixed with "ejb/". - -Used in: ejb-ref - -Example: - <ejb-ref-name>ejb/Payroll</ejb-ref-name> ---> -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected type of the referenced -enterprise bean. - -The ejb-ref-type element must be one of the following: - <ejb-ref-type>Entity</ejb-ref-type> - <ejb-ref-type>Session</ejb-ref-type> - -Used in: ejb-ref ---> -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- -The enterprise-beans element contains the declarations of one or more -enterprise beans. ---> -<!ELEMENT enterprise-beans (session | entity)+> - -<!-- -The entity element declares an entity bean. The declaration consists -of: an optional description; optional display name; optional small icon -file name; optional large icon file name; a name assigned to the -enterprise bean in the deployment descriptor; the names of the entity -bean's home and remote interfaces; the entity bean's implementation -class; the entity bean's persistence management type; the entity bean's -primary key class name; an indication of the entity bean's reentrancy; -an optional list of container-managed fields; an optional specification -of the primary key field; an optional declaration of the bean's -environment entries; an optional declaration of the bean's EJB -references; an optional declaration of the security role references; -and an optional declaration of the bean's resource manager connection -factory references. - -The optional primkey-field may be present in the descriptor if the -entity's persistency-type is Container. - -The other elements that are optional are "optional" in the sense that -they are omitted if the lists represented by them are empty. - -At least one cmp-field element must be present in the descriptor if the -entity's persistency-type is Container, and none must not be present if -the entity's persistence-type is Bean. - -Used in: enterprise-beans ---> -<!ELEMENT entity (description?, display-name?, small-icon?, - large-icon?, ejb-name, home, remote, ejb-class, - persistence-type, prim-key-class, reentrant, - cmp-field*, primkey-field?, env-entry*, - ejb-ref*, security-role-ref*, resource-ref*)> - -<!-- -The env-entry element contains the declaration of an enterprise bean's -environment entries. The declaration consists of an optional -description, the name of the environment entry, and an optional value. - -Used in: entity and session ---> -<!ELEMENT env-entry (description?, env-entry-name, env-entry-type, - env-entry-value?)> - -<!-- -The env-entry-name element contains the name of an enterprise bean's -environment entry. - -Used in: env-entry - -Example: - <env-entry-name>minAmount</env-entry-name> ---> -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-type element contains the fully-qualified Java type of -the environment entry value that is expected by the enterprise bean's -code. - -The following are the legal values of env-entry-type: -java.lang.Boolean, java.lang.String, java.lang.Integer, -java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and -java.lang.Float. - -Used in: env-entry - -Example: - <env-entry-type>java.lang.Boolean</env-entry-type> ---> -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The env-entry-value element contains the value of an enterprise bean's -environment entry. - -Used in: env-entry - -Example: - <env-entry-value>100.00</env-entry-value> ---> -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The field-name element specifies the name of a container managed field. -The name must be a public field of the enterprise bean class or one of -its superclasses. - -Used in: cmp-field - -Example: - <field-name>firstName</field-Name> ---> -<!ELEMENT field-name (#PCDATA)> - -<!-- -The home element contains the fully-qualified name of the enterprise -bean's home interface. - -Used in: ejb-ref, entity, and session - -Example: - <home>com.aardvark.payroll.PayrollHome</home> ---> -<!ELEMENT home (#PCDATA)> - -<!-- -The large-icon element contains the name of a file containing a large -(32 x 32) icon image. The file name is relative path within the ejb-jar -file. - -The image must be either in the JPEG or GIF format, and the file name -must end with the suffix ".jpg" or ".gif" respectively. The icon can -be used by tools. - -Example: - <large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The method element is used to denote a method of an enterprise bean's -home or remote interface, or a set of methods. The ejb-name element -must be the name of one of the enterprise beans in declared in the -deployment descriptor; the optional method-intf element allows to -distinguish between a method with the same signature that is defined in -both the home and remote interface; the method-name element specifies -the method name; and the optional method-params elements identify a -single method among multiple methods with an overloaded method name. - -There are three possible styles of the method element syntax: - -1. <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>*</method-name> - </method> - - This style is used to refer to all the methods of the specified - enterprise bean's home and remote interfaces. - -2. <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - </method>> - - This style is used to refer to the specified method of the - specified enterprise bean. If there are multiple methods with - the same overloaded name, the element of this style refers to - all the methods with the overloaded name. - - - - - -3. <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - <method-params> - <method-param>PARAM-1</method-param> - <method-param>PARAM-2</method-param> - ... - <method-param>PARAM-n</method-param> - </method-params> - <method> - - This style is used to refer to a single method within a set of - methods with an overloaded name. PARAM-1 through PARAM-n are the - fully-qualified Java types of the method's input parameters (if - the method has no input arguments, the method-params element - contains no method-param elements). Arrays are specified by the - array element's type, followed by one or more pair of square - brackets (e.g. int[][]). - - -Used in: method-permission and container-transaction - -Examples: - - Style 1: The following method element refers to all the methods of - the EmployeeService bean's home and remote interfaces: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>*</method-name> - </method> - - Style 2: The following method element refers to all the create - methods of the EmployeeService bean's home interface: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - </method> - - Style 3: The following method element refers to the - create(String firstName, String LastName) method of the - EmployeeService bean's home interface. - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - - The following example illustrates a Style 3 element with - more complex parameter types. The method - foobar(char s, int i, int[] iar, mypackage.MyClass mycl, - mypackage.MyClass[][] myclaar) - would be specified as: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>foobar</method-name> - <method-params> - <method-param>char</method-param> - <method-param>int</method-param> - <method-param>int[]</method-param> - <method-param>mypackage.MyClass</method-param> - <method-param>mypackage.MyClass[][]</method-param> - </method-params> - </method> - - The optional method-intf element can be used when it becomes - necessary to differentiate between a method defined in the home - interface and a method with the same name and signature that is - defined in the remote interface. - - For example, the method element - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Remote</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - can be used to differentiate the create(String, String) method - defined in the remote interface from the create(String, String) - method defined in the home interface, which would be defined as - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - ---> -<!ELEMENT method (description?, ejb-name, method-intf?, method-name, - method-params?)> - -<!-- -The method-intf element allows a method element to differentiate -between the methods with the same name and signature that are defined -in both the remote and home interfaces. - -The method-intf element must be one of the following: - <method-intf>Home</method-intf> - <method-intf>Remote</method-intf> - -Used in: method ---> -<!ELEMENT method-intf (#PCDATA)> - -<!-- -The method-name element contains a name of an enterprise bean method, -or the asterisk (*) character. The asterisk is used when the element -denotes all the methods of an enterprise bean's remote and home -interfaces. - -Used in: method ---> -<!ELEMENT method-name (#PCDATA)> - -<!-- -The method-param element contains the fully-qualified Java type name of -a method parameter. - -Used in: method-params ---> -<!ELEMENT method-param (#PCDATA)> - -<!-- -The method-params element contains a list of the fully-qualified Java -type names of the method parameters. - -Used in: method ---> -<!ELEMENT method-params (method-param*)> - -<!-- -The method-permission element specifies that one or more security roles -are allowed to invoke one or more enterprise bean methods. The -method-permission element consists of an optional description, a list -of security role names, and a list of method elements. - -The security roles used in the method-permission element must be -defined in the security-role element of the deployment descriptor, and -the methods must be methods defined in the enterprise bean's remote -and/or home interfaces. - -Used in: assembly-descriptor ---> -<!ELEMENT method-permission (description?, role-name+, method+)> - -<!-- -The persistence-type element specifies an entity bean's persistence -management type. - -The persistence-type element must be one of the two following: - <persistence-type>Bean</persistence-type> - <persistence-type>Container</persistence-type> - -Used in: entity ---> -<!ELEMENT persistence-type (#PCDATA)> - -<!-- -The prim-key-class element contains the fully-qualified name of an -entity bean's primary key class. - -If the definition of the primary key class is deferred to deployment -time, the prim-key-class element should specify java.lang.Object. - -Used in: entity - -Examples: - <prim-key-class>java.lang.String</prim-key-class> - <prim-key-class>com.wombat.empl.EmployeeID</prim-key-class> - <prim-key-class>java.lang.Object</prim-key-class> - ---> -<!ELEMENT prim-key-class (#PCDATA)> - -<!-- -The primkey-field element is used to specify the name of the primary -key field for an entity with container-managed persistence. - -The primkey-field must be one of the fields declared in the cmp-field -element, and the type of the field must be the same as the primary key -type. - -The primkey-field element is not used if the primary key maps to -multiple container-managed fields (i.e. the key is a compound key). In -this case, the fields of the primary key class must be public, and -their names must correspond to the field names of the entity bean class -that comprise the key. - -Used in: entity - -Example: - <primkey-field>EmployeeId</primkey-field> ---> -<!ELEMENT primkey-field (#PCDATA)> - -<!-- -The reentrant element specifies whether an entity bean is reentrant or not. - -The reentrant element must be one of the two following: - <reentrant>True</reentrant> - <reentrant>False</reentrant> - -Used in: entity ---> -<!ELEMENT reentrant (#PCDATA)> - -<!-- -The remote element contains the fully-qualified name of the enterprise -bean's remote interface. - -Used in: ejb-ref, entity, and session - -Example: - <remote>com.wombat.empl.EmployeeService</remote> ---> -<!ELEMENT remote (#PCDATA)> - -<!-- -The res-auth element specifies whether the enterprise bean code signs -on programmatically to the resource manager, or whether the Container -will sign on to the resource manager on behalf of the bean. In the -latter case, the Container uses information that is supplied by the -Deployer. - -The value of this element must be one of the two following: - <res-auth>Application</res-auth> - <res-auth>Container</res-auth> ---> -<!ELEMENT res-auth (#PCDATA)> - -<!-- -The res-ref-name element specifies the name of a resource manager -connection factory reference. - -Used in: resource-ref ---> -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-type element specifies the type of the data source. The type is -specified by the Java interface (or class) expected to be implemented -by the data source. - -Used in: resource-ref ---> -<!ELEMENT res-type (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of enterprise bean's -reference to an external resource. It consists of an optional -description, the resource manager connection factory reference name, -the indication of the resource manager connection factory type expected -by the enterprise bean code, and the type of authentication (bean or -container). - -Used in: entity and session - -Example: - <resource-ref> - <res-ref-name>EmployeeAppDB</res-ref-name> - <res-type>javax.sql.DataSource</res-type> - <res-auth>Container</res-auth> - </resource-ref> ---> -<!ELEMENT resource-ref (description?, res-ref-name, res-type, - res-auth)> - -<!-- -The role-link element is used to link a security role 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. - -Used in: security-role-ref ---> -<!ELEMENT role-link (#PCDATA)> - -<!-- -The role-name element contains the name of a security role. - -The name must conform to the lexical rules for an NMTOKEN. - -Used in: method-permission, security-role, and security-role-ref ---> -<!ELEMENT role-name (#PCDATA)> - -<!-- -The security-role element contains the definition of a security role. -The definition consists of an optional description of the security -role, and the security role name. - -Used in: assembly-descriptor - -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> ---> -<!ELEMENT security-role (description?, role-name)> - -<!-- -The security-role-ref element contains the declaration of a security -role reference in the enterprise bean's code. The declaration consists -of an optional description, the security role name used in the code, -and an optional link to a defined security role. - -The value of the role-name element must be the String used as the -parameter to the EJBContext.isCallerInRole(String roleName) method. - -The value of the role-link element must be the name of one of the -security roles defined in the security-role elements. - -Used in: entity and session - ---> -<!ELEMENT security-role-ref (description?, role-name, role-link?)> - -<!-- -The session-type element describes whether the session bean is a -stateful session, or stateless session. - -The session-type element must be one of the two following: - <session-type>Stateful</session-type> - <session-type>Stateless</session-type> ---> -<!ELEMENT session-type (#PCDATA)> - -<!-- -The session element declares an session bean. The declaration consists -of: an optional description; optional display name; optional small icon -file name; optional large icon file name; a name assigned to the -enterprise bean in the deployment description; the names of the session -bean's home and remote interfaces; the session bean's implementation -class; the session bean's state management type; the session bean's -transaction management type; an optional declaration of the bean's -environment entries; an optional declaration of the bean's EJB -references; an optional declaration of the security role references; -and an optional declaration of the bean's resource manager connection -factory references. - -The elements that are optional are "optional" in the sense that they -are omitted when if lists represented by them are empty. - -Used in: enterprise-beans ---> -<!ELEMENT session (description?, display-name?, small-icon?, - large-icon?, ejb-name, home, remote, ejb-class, - session-type, transaction-type, env-entry*, - ejb-ref*, security-role-ref*, resource-ref*)> - -<!-- -The small-icon element contains the name of a file containing a small -(16 x 16) icon image. The file name is relative path within the ejb-jar -file. - -The image must be either in the JPEG or GIF format, and the file name -must end with the suffix ".jpg" or ".gif" respectively. - -The icon can be used by tools. - -Example: - <small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The transaction-type element specifies an enterprise bean's transaction -management type. - -The transaction-type element must be one of the two following: - <transaction-type>Bean</transaction-type> - <transaction-type>Container</transaction-type> - -Used in: session ---> -<!ELEMENT transaction-type (#PCDATA)> - -<!-- -The trans-attribute element specifies how the container must manage the -transaction boundaries when delegating a method invocation to an -enterprise bean's business method. - -The value of trans-attribute must be one of the following: - <trans-attribute>NotSupported</trans-attribute> - <trans-attribute>Supports</trans-attribute> - <trans-attribute>Required</trans-attribute> - <trans-attribute>RequiresNew</trans-attribute> - <trans-attribute>Mandatory</trans-attribute> - <trans-attribute>Never</trans-attribute> - -Used in: container-transaction ---> -<!ELEMENT trans-attribute (#PCDATA)> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e information beyond the standard EJB deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tools-specific files to the -information in the standard deployment descriptor. - -The EJB architecture does not allow the tools to add the non-standard -information into the EJB deployment descriptor. ---> -<!ATTLIST assembly-descriptor id ID #IMPLIED> -<!ATTLIST cmp-field id ID #IMPLIED> -<!ATTLIST container-transaction id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb-class id ID #IMPLIED> -<!ATTLIST ejb-client-jar id ID #IMPLIED> -<!ATTLIST ejb-jar id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> -<!ATTLIST ejb-name id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST enterprise-beans id ID #IMPLIED> -<!ATTLIST entity id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST field-name id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST method id ID #IMPLIED> -<!ATTLIST method-intf id ID #IMPLIED> -<!ATTLIST method-name id ID #IMPLIED> -<!ATTLIST method-param id ID #IMPLIED> -<!ATTLIST method-params id ID #IMPLIED> -<!ATTLIST method-permission id ID #IMPLIED> -<!ATTLIST persistence-type id ID #IMPLIED> -<!ATTLIST prim-key-class id ID #IMPLIED> -<!ATTLIST primkey-field id ID #IMPLIED> -<!ATTLIST reentrant id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST role-link id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST security-role-ref id ID #IMPLIED> -<!ATTLIST session-type id ID #IMPLIED> -<!ATTLIST session id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST transaction-type id ID #IMPLIED> -<!ATTLIST trans-attribute id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_0.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_0.dtd deleted file mode 100644 index 9a2cc7ce76..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_0.dtd +++ /dev/null @@ -1,1671 +0,0 @@ -<!-- -Copyright (c) 2000 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 embodied in the product that is 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 in other countries. - -This document and the product to which it pertains are distributed -under licenses restricting their use, copying, distribution, and -decompilation. This document may be reproduced and distributed but may -not be changed 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, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and and -Enterprise JavaBeans 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. - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED -WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR -NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH -DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. - - -_________________________________________________________________________ - -Copyright (c) 2000 Sun Microsystems, Inc., -901 San Antonio Road, -Palo Alto, California 94303, E'tats-Unis. -Tous droits re'serve's. - -Sun Microsystems, Inc. a les droits de proprie'te' intellectuels -relatants a` la technologie incorpore'e dans le produit qui est de'crit -dans ce document. En particulier, et sans la limitation, ces droits de -proprie'te' intellectuels peuvent inclure un ou plus des brevets -ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les -brevets plus supple'mentaires ou les applications de brevet en attente -dans les E'tats-Unis et dans les autres pays. - -Ce produit ou document est prote'ge' par un copyright et distribue' -avec des licences qui en restreignent l'utilisation, la copie, la -distribution, et la de'compilation. Ce documention associe n peut -e^tre reproduite et distribuer, par quelque moyen que ce soit, sans -l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de -licence, le cas e'che'ant. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright et -licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail et and -Enterprise JavaBeans sont des marques de fabrique ou des marques -de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres -pays. - -LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT -EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS -NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A -L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE -CONTREFAC,ON. ---> - -<!-- -This is the XML DTD for the EJB 2.0 deployment descriptor. -All EJB 2.0 deployment descriptors must include a DOCTYPE -of the following form: - - <!DOCTYPE ejb-jar PUBLIC - "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" - "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> - ---> - -<!-- -The following conventions apply to all J2EE deployment descriptor -elements unless indicated otherwise. - -- In elements that contain PCDATA, leading and trailing whitespace - in the data may be ignored. - -- In elements whose value is an "enumerated type", the value is - case sensitive. - -- 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 ejb-jar element is the root element of the EJB deployment -descriptor. It contains - - - an optional description of the ejb-jar file - - an optional display name - - an optional small icon file name - - an optional large icon file name - - mandatory structural information about all included - enterprise beans - - a descriptor for container managed relationships, if any - - an optional application-assembly descriptor - - an optional name of an ejb-client-jar file for the ejb-jar. ---> -<!ELEMENT ejb-jar (description?, display-name?, small-icon?, -large-icon?, enterprise-beans, relationships?, assembly-descriptor?, -ejb-client-jar?)> - -<!-- -The abstract-schema-name element specifies the name of the abstract -schema type of an entity bean with cmp-version 2.x. It is used in EJB -QL queries. - -For example, the abstract-schema-name for an entity bean whose local -interface is com.acme.commerce.Order might be Order. - -Used in: entity ---> -<!ELEMENT abstract-schema-name (#PCDATA)> - -<!-- - -The acknowledge-mode element specifies whether JMS AUTO_ACKNOWLEDGE or -DUPS_OK_ACKNOWLEDGE message acknowledgment semantics should be used -for the onMessage message of a message-driven bean that uses bean -managed transaction demarcation. - -The acknowledge-mode element must be one of the two following: - - <acknowledge-mode>Auto-acknowledge</acknowledge-mode> - <acknowledge-mode>Dups-ok-acknowledge</acknowledgemode> - -Used in: message-driven ---> -<!ELEMENT acknowledge-mode (#PCDATA)> - -<!-- -The assembly-descriptor element contains application-assembly information. - -The application-assembly information consists of the following parts: -the definition of security roles, the definition of method -permissions, the definition of transaction attributes for -enterprise beans with container-managed transaction demarcation and -a list of methods to be excluded from being invoked. - -All the parts are optional in the sense that they are omitted if the -lists represented by them are empty. - -Providing an assembly-descriptor in the deployment descriptor is -optional for the ejb-jar file producer. - -Used in: ejb-jar ---> -<!ELEMENT assembly-descriptor (security-role*, method-permission*, -container-transaction*, exclude-list?)> - -<!-- -The cascade-delete element specifies that, within a particular -relationship, the lifetime of one or more entity beans is dependent -upon the lifetime of another entity bean. The cascade-delete element -can only be specified for an ejb-relationship-role element contained -in an ejb-relation element in which the other ejb-relationship-role -element specifies a multiplicity of One. - -Used in: ejb-relationship-role ---> -<!ELEMENT cascade-delete EMPTY> - -<!-- -The cmp-field element describes a container-managed field. The -field element includes an optional description of the field, and the -name of the field. - -Used in: entity ---> -<!ELEMENT cmp-field (description?, field-name)> - -<!-- -The cmp-version element specifies the version of an entity bean -with container-managed persistence. - -The cmp-version element must be one of the two following: - - <cmp-version>1.x</cmp-version> - <cmp-version>2.x</cmp-version> - -The default value of the cmp-version element is 2.x. - -Used in: entity ---> -<!ELEMENT cmp-version (#PCDATA)> - -<!-- - -The cmr-field element describes the bean provider's view of a -relationship. It consists of an optional description, and the name and -the class type of a field in the source of a role of a -relationship. The cmr-field-name element corresponds to the name used -for the get and set accessor methods for the relationship. The -cmr-field-type element is used only for collection-valued -cmr-fields. It specifies the type of the collection that is used. - -Used in: ejb-relationship-role ---> -<!ELEMENT cmr-field (description?, cmr-field-name, cmr-field-type?)> - -<!-- -The cmr-field-name element specifies the name of a logical -relationship field in the entity bean class. The name of the cmr-field -must begin with a lowercase letter. This field is accessed by methods -whose names consist of the name of the field specified by -cmr-field-name in which the first letter is uppercased, prefixed by -"get" or "set". - -Used in: cmr-field ---> -<!ELEMENT cmr-field-name (#PCDATA)> - -<!-- -The cmr-field-type element specifies the class of a -collection-valued logical relationship field in the entity bean -class. The value of the cmr-field-type element must be either: -java.util.Collection or java.util.Set. - -Used in: cmr-field ---> -<!ELEMENT cmr-field-type (#PCDATA)> - -<!-- -The container-transaction element specifies how the container -must manage transaction scopes for the enterprise bean's method -invocations. The element consists of an optional description, a list -of method elements, and a transaction attribute. The transaction -attribute is to be applied to all the specified methods. - -Used in: assembly-descriptor ---> -<!ELEMENT container-transaction (description?, method+, trans-attribute)> - -<!-- -The description element is used to provide text describing the parent -element. The description element should include any information that -the enterprise bean ejb-jar file producer wants to provide to the consumer of -the enterprise bean ejb-jar file (i.e., to the Deployer). Typically, the tools -used by the enterprise bean ejb-jar file consumer will display the description -when processing the parent element that contains the description. - -Used in: cmp-field, cmr-field, container-transaction, ejb-jar, -ejb-local-ref, ejb-ref, ejb-relation, ejb-relationship-role, entity, -env-entry, exclude-list, message-driven, method, method-permission, -query, relationship-role-source, relationships, resource-env-ref, -resource-ref, run-as, security-identity, security-role, -security-role-ref, session ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The destination-type element specifies the type of the JMS -destination. The type is specified by the Java interface expected to -be implemented by the destination. - -The destination-type element must be one of the two following: - -<destination-type>javax.jms.Queue</destination-type> -<destination-type>javax.jms.Topic</destination-type> - -Used in: message-driven-destination ---> -<!ELEMENT destination-type (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -displayed by tools. The display name need not be unique. - -Used in: ejb-jar, entity, message-driven, session - -Example: - -<display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The ejb-class element contains the fully-qualified name of the -enterprise bean's class. - -Used in: entity, message-driven, session - -Example: - -<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class> ---> -<!ELEMENT ejb-class (#PCDATA)> - -<!-- -The optional ejb-client-jar element specifies a JAR file that contains -the class files necessary for a client program to access the -enterprise beans in the ejb-jar file. - -Used in: ejb-jar - -Example: - -<ejb-client-jar>employee_service_client.jar</ejb-client-jar> ---> -<!ELEMENT ejb-client-jar (#PCDATA)> - -<!-- -The ejb-link element is used in the ejb-ref or ejb-local-ref -elements to specify that an EJB reference is linked to an -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 J2EE 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 ejb-jar file -containing the enterprise bean that is referencing the enterprise bean. -This allows multiple enterprise beans with the same ejb-name to be -uniquely identified. - -Used in: ejb-local-ref, ejb-ref - -Examples: - - <ejb-link>EmployeeRecord</ejb-link> - - <ejb-link>../products/product.jar#ProductEJB</ejb-link> - ---> -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ejb-local-ref element is used for the declaration of a reference to -an enterprise bean's local home. The declaration consists of: - - - an optional description - - the EJB reference name used in the code of the enterprise bean - that's referencing the enterprise bean - - the expected type of the referenced enterprise bean - - the expected local home and local interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the referenced - enterprise bean - -Used in: entity, message-driven, session ---> -<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type, - local-home, local, ejb-link?)> - -<!-- -The ejb-name element specifies an enterprise bean's name. This name is -assigned by the ejb-jar file producer to name the enterprise bean in -the ejb-jar file's deployment descriptor. The name must be unique -among the names of the enterprise beans in the same ejb-jar file. - -There is no architected relationship between the ejb-name in the -deployment descriptor and the JNDI name that the Deployer will assign -to the enterprise bean's home. - -The name for an entity bean with cmp-version 2.x must conform to the -lexical rules for an NMTOKEN. The name for an entity bean with -cmp-version 2.x must not be a reserved literal in EJB QL. - -Used in: entity, message-driven, method, relationship-role-source, -session - -Example: - -<ejb-name>EmployeeService</ejb-name> ---> -<!ELEMENT ejb-name (#PCDATA)> - -<!-- -The ejb-ql element contains the EJB QL query string that defines -a finder or select query. This element is defined within the scope of -a query element whose contents specify the finder or the select method -that uses the query. The content must be a valid EJB QL query string -for the entity bean for which the query is specified. - -The ejb-ql element must be specified for all queries that are -expressible in EJB QL. - -Used in: query - -Example: -<query> - <query-method> - <method-name>ejbSelectPendingLineitems</method-name> - <method-params/> - </query-method> - <ejb-ql>SELECT OBJECT(l) FROM LineItems l WHERE l.shipped <> TRUE - </ejb-ql> -</query> - ---> -<!ELEMENT ejb-ql (#PCDATA)> - -<!-- -The ejb-ref element is used for the declaration of a reference to -an enterprise bean's home. The declaration consists of: - - - an optional description - - the EJB reference name used in the code of - the enterprise bean that's referencing the enterprise bean - - the expected type of the referenced enterprise bean - - the expected home and remote interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the referenced - enterprise bean - -Used in: entity, message-driven, session ---> -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, - home, remote, ejb-link?)> - -<!-- -The ejb-ref-name element contains the name of an EJB reference. The -EJB reference is an entry in the enterprise bean's environment and is -relative to the java:comp/env context. The name must be unique -within the enterprise bean. - -It is recommended that name is prefixed with "ejb/". - -Used in: ejb-local-ref, ejb-ref - -Example: - -<ejb-ref-name>ejb/Payroll</ejb-ref-name> ---> -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected type of the -referenced enterprise bean. - -The ejb-ref-type element must be one of the following: - - <ejb-ref-type>Entity</ejb-ref-type> - <ejb-ref-type>Session</ejb-ref-type> - -Used in: ejb-local-ref, ejb-ref ---> -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- - -The ejb-relation element describes a relationship between two -entity beans with container-managed persistence. An ejb-relation -element contains a description; an optional ejb-relation-name element; -and exactly two relationship role declarations, defined by the -ejb-relationship-role elements. The name of the relationship, if -specified, is unique within the ejb-jar file. - -Used in: relationships ---> -<!ELEMENT ejb-relation (description?, ejb-relation-name?, ejb-relationship-role, -ejb-relationship-role)> - -<!-- -The ejb-relation-name element provides a unique name for a relationship. - -Used in: ejb-relation ---> -<!ELEMENT ejb-relation-name (#PCDATA)> - -<!-- -The ejb-relationship-role element describes a role within a -relationship. There are two roles in each relationship. - -The ejb-relationship-role element contains an optional description; an -optional name for the relationship role; a specification of the -multiplicity of the role; an optional specification of cascade-delete -functionality for the role; the role source; and a declaration of the -cmr-field, if any, by means of which the other side of the -relationship is accessed from the perspective of the role source. - -The multiplicity and role-source element are mandatory. - -The relationship-role-source element designates an entity bean by -means of an ejb-name element. For bidirectional relationships, both -roles of a relationship must declare a relationship-role-source -element that specifies a cmr-field in terms of which the relationship -is accessed. The lack of a cmr-field element in an -ejb-relationship-role specifies that the relationship is -unidirectional in navigability and the entity bean that participates -in the relationship is "not aware" of the relationship. - -Used in: ejb-relation - -Example: - -<ejb-relation> - <ejb-relation-name>Product-LineItem</ejb-relation-name> - <ejb-relationship-role> - <ejb-relationship-role-name>product-has-lineitems - </ejb-relationship-role-name> - <multiplicity>One</multiplicity> - <relationship-role-source> - <ejb-name>ProductEJB</ejb-name> - </relationship-role-source> - </ejb-relationship-role> - ---> -<!ELEMENT ejb-relationship-role (description?, ejb-relationship-role-name?, -multiplicity, cascade-delete?, relationship-role-source, cmr-field?)> - -<!-- -The ejb-relationship-role-name element defines a name for a role that -is unique within an ejb-relation. Different relationships can use the -same name for a role. - -Used in: ejb-relationship-role ---> -<!ELEMENT ejb-relationship-role-name (#PCDATA)> - -<!-- -The enterprise-beans element contains the declarations of one or more -enterprise beans. ---> -<!ELEMENT enterprise-beans (session | entity | message-driven)+> - -<!-- -The entity element declares an entity bean. The declaration -consists of: - - - an optional description - - an optional display name - - an optional small icon file name - - an optional large icon file name - - a unique name assigned to the enterprise bean - in the deployment descriptor - - the names of the entity bean's remote home and remote - interfaces, if any - - the names of the entity bean's local home and local - interfaces, if any - - the entity bean's implementation class - - the entity bean's persistence management type - - the entity bean's primary key class name - - an indication of the entity bean's reentrancy - - an optional specification of the entity bean's cmp-version - - an optional specification of the entity bean's abstract - schema name - - an optional list of container-managed fields - - an optional specification of the primary key field - - an optional declaration of the bean's environment entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local EJB references - - an optional declaration of the security role references - - an optional declaration of the security identity - to be used for the execution of the bean's methods - - an optional declaration of the bean's resource manager - connection factory references - - an optional declaration of the bean's - resource environment references - - an optional set of query declarations - for finder and select methods for an entity - bean with cmp-version 2.x. - -The optional abstract-schema-name element must be specified for an -entity bean with container-managed persistence and cmp-version 2.x. - -The optional primkey-field may be present in the descriptor if the -entity's persistence-type is Container. - -The optional cmp-version element may be present in the descriptor if -the entity's persistence-type is Container. If the persistence-type is -Container and the cmp-version element is not specified, its value -defaults to 2.x. - -The optional home and remote elements must be specified if the entity -bean cmp-version is 1.x. - -The optional home and remote elements must be specified if the entity -bean has a remote home and remote interface. - -The optional local-home and local elements must be specified if the -entity bean has a local home and local interface. - -Either both the local-home and the local elements or both the -home and the remote elements must be specified. - -The optional query elements must be present if the persistence-type is -Container and the cmp-version is 2.x and query methods other than -findByPrimaryKey have been defined for the entity bean. - -The other elements that are optional are "optional" in the sense that -they are omitted if the lists represented by them are empty. - -At least one cmp-field element must be present in the descriptor if -the entity's persistence-type is Container and the cmp-version is 1.x, -and none must not be present if the entity's persistence-type is Bean. - -Used in: enterprise-beans - ---> -<!ELEMENT entity (description?, display-name?, small-icon?, - large-icon?, ejb-name, home?, remote?, local-home?, - local?, ejb-class, persistence-type, prim-key-class, - reentrant, cmp-version?, abstract-schema-name?, - cmp-field*, primkey-field?, env-entry*, ejb-ref*, - ejb-local-ref*, security-role-ref*, security-identity?, - resource-ref*, resource-env-ref*, query*)> - -<!-- -The env-entry element contains the declaration of an enterprise bean's -environment entry. The declaration consists of an optional -description, the name of the environment entry, and an optional -value. If a value is not specified, one must be supplied -during deployment. - -Used in: entity, message-driven, session ---> -<!ELEMENT env-entry (description?, env-entry-name, env-entry-type, - env-entry-value?)> - -<!-- -The env-entry-name element contains the name of an enterprise bean's -environment entry. The name is a JNDI name relative to the -java:comp/env context. The name must be unique within an enterprise bean. - -Used in: env-entry - -Example: - -<env-entry-name>minAmount</env-entry-name> ---> -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-type element contains the fully-qualified Java type of -the environment entry value that is expected by the enterprise bean's -code. - -The following are the legal values of env-entry-type: - - 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 - - -Used in: env-entry - -Example: - -<env-entry-type>java.lang.Boolean</env-entry-type> ---> -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The env-entry-value element contains the value of an enterprise bean'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. - -Used in: env-entry - -Example: - -<env-entry-value>100.00</env-entry-value> ---> -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The exclude list element specifies one or more methods which the -Assembler marks to be uncallable. - -If the method permission relation contains methods that are in the -exclude list, the Deployer should consider those methods to be -uncallable. - -Used in: assembly-descriptor ---> -<!ELEMENT exclude-list (description?, method+)> - -<!-- -The field-name element specifies the name of a container managed -field. - -The name of the cmp-field of an entity bean with cmp-version 2.x must -begin with a lowercase letter. This field is accessed by methods whose -names consists of the name of the field specified by field-name in -which the first letter is uppercased, prefixed by "get" or "set". - -The name of the cmp-field of an entity bean with cmp-version 1.x must -denote a public field of the enterprise bean class or one of its -superclasses. - -Used in: cmp-field - -Example: - - - <field-name>firstName</field-Name> - ---> -<!ELEMENT field-name (#PCDATA)> - -<!-- -The home element contains the fully-qualified name of the enterprise -bean's home interface. - -Used in: ejb-ref, entity, session - -Example: - -<home>com.aardvark.payroll.PayrollHome</home> ---> -<!ELEMENT home (#PCDATA)> - -<!-- -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 enterprise bean's -ejb-jar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: ejb-jar, entity, message-driven, session - -Example: - -<large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- - -The local element contains the fully-qualified name of the -enterprise bean's local interface. - -Used in: ejb-local-ref, entity, session - ---> -<!ELEMENT local (#PCDATA)> - -<!-- - -The local-home element contains the fully-qualified name of the -enterprise bean's local home interface. - -Used in: ejb-local-ref, entity, session ---> -<!ELEMENT local-home (#PCDATA)> - -<!-- - -The message-driven element declares a message-driven bean. The -declaration consists of: - - - an optional description - - an optional display name - - an optional small icon file name - - an optional large icon file name - - a name assigned to the enterprise bean in - the deployment descriptor - - the message-driven bean's implementation class - - the message-driven bean's transaction management type - - an optional declaration of the message-driven bean's - message selector - - an optional declaration of the - acknowledgment mode for the message-driven bean - if bean-managed transaction demarcation is used - - an optional declaration of the - intended destination type of the message-driven bean - - an optional declaration of the bean's environment entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local EJB references - - an optional declaration of the security - identity to be used for the execution of the bean's methods - - an optional declaration of the bean's resource manager - connection factory references - - an optional declaration of the bean's resource - environment references. - -Used in: enterprise-beans ---> -<!ELEMENT message-driven (description?, display-name?, small-icon?, - large-icon?, ejb-name, ejb-class, transaction-type, - message-selector?, acknowledge-mode?, - message-driven-destination?, env-entry*, ejb-ref*, - ejb-local-ref*, security-identity?, resource-ref*, - resource-env-ref*)> - -<!-- -The message-driven-destination element provides advice to the Deployer -as to whether a message-driven bean is intended for a Queue or a -Topic. The declaration consists of: the type of the message-driven -bean's intended destination and an optional declaration of whether a -durable or non-durable subscription should be used if the -destination-type is javax.jms.Topic. - -Used in: message-driven ---> -<!ELEMENT message-driven-destination (destination-type, -subscription-durability?)> - -<!-- -The message-selector element is used to specify the JMS message -selector to be used in determining which messages a message-driven -bean is to receive. - -Example: -<message-selector>JMSType = `car' AND color = `blue' AND weight > 2500 -</message-selector> - -Used in: message-driven ---> -<!ELEMENT message-selector (#PCDATA)> - -<!-- - -The method element is used to denote a method of an enterprise -bean's home or component interface, or, in the case of a message-driven -bean, the bean's onMessage method, or a set of methods. The ejb-name -element must be the name of one of the enterprise beans declared in -the deployment descriptor; the optional method-intf element allows to -distinguish between a method with the same signature that is multiply -defined across in both the home and component interfaces; the -method-name element specifies the method name; and the optional -method-params elements identify a single method among multiple methods -with an overloaded method name. - -There are three possible styles of the method element syntax: - -1. -<method> - <ejb-name>EJBNAME</ejb-name> - <method-name>*</method-name> -</method> - - This style is used to refer to all the methods of the specified - enterprise bean's home and component interfaces. - -2. -<method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> -</method>> - - This style is used to refer to the specified method of the - specified enterprise bean. If there are multiple methods with - the same overloaded name, the element of this style refers to - all the methods with the overloaded name. - - -3. -<method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - <method-params> - <method-param>PARAM-1</method-param> - <method-param>PARAM-2</method-param> - ... - <method-param>PARAM-n</method-param> - </method-params> -<method> - - - This style is used to refer to a single method within a set of - methods with an overloaded name. PARAM-1 through PARAM-n are the - fully-qualified Java types of the method's input parameters (if - the method has no input arguments, the method-params element - contains no method-param elements). Arrays are specified by the - array element's type, followed by one or more pair of square - brackets (e.g. int[][]). If there are multiple methods with the - same overloaded name, this style refers to all of the overloaded - methods. - - -Used in: container-transaction, exclude-list, method-permission - -Examples: - -Style 1: The following method element refers to all the methods of -the EmployeeService bean's home and component interfaces: - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-name>*</method-name> -</method> - -Style 2: The following method element refers to all the create -methods of the EmployeeService bean's home interface(s). - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> -</method> - - -Style 3: The following method element refers to the -create(String firstName, String LastName) method of the -EmployeeService bean's home interface(s). - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> -</method> - - -The following example illustrates a Style 3 element with -more complex parameter types. The method -foobar(char s, int i, int[] iar, mypackage.MyClass mycl, -mypackage.MyClass[][] myclaar) would be specified as: - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-name>foobar</method-name> - <method-params> - <method-param>char</method-param> - <method-param>int</method-param> - <method-param>int[]</method-param> - <method-param>mypackage.MyClass</method-param> - <method-param>mypackage.MyClass[][]</method-param> - </method-params> -</method> - - -The optional method-intf element can be used when it becomes necessary -to differentiate between a method that is multiply defined across the -enterprise bean's home and component interfaces with the same name and -signature. - - -For example, the method element - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Remote</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> -</method> - - -can be used to differentiate the create(String, String) method defined -in the remote interface from the create(String, String) method defined -in the remote home interface, which would be defined as - - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> -</method> - -and the create method that is defined in the local home interface -which would be defined as - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>LocalHome</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> -</method> - - -The method-intf element can be used with all three Styles of the -method element usage. For example, the following method element -example could be used to refer to all the methods of the -EmployeeService bean's remote home interface. - - -<method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>*</method-name> -</method> - ---> -<!ELEMENT method (description?, ejb-name, method-intf?, method-name, -method-params?)> - -<!-- - -The method-intf element allows a method element to differentiate -between the methods with the same name and signature that are multiply -defined across the component and home interfaces (e.g, in both an -enterprise bean's remote and local interfaces; in both an enterprise bean's -home and remote interfaces, etc.) - -The method-intf element must be one of the following: - - <method-intf>Home</method-intf> - <method-intf>Remote</method-intf> - <method-intf>LocalHome</method-intf> - <method-intf>Local</method-intf> - -Used in: method ---> -<!ELEMENT method-intf (#PCDATA)> - -<!-- -The method-name element contains a name of an enterprise bean method -or the asterisk (*) character. The asterisk is used when the element -denotes all the methods of an enterprise bean's component and home -interfaces. - -Used in: method, query-method ---> -<!ELEMENT method-name (#PCDATA)> - -<!-- -The method-param element contains the fully-qualified Java type name -of a method parameter. - -Used in: method-params ---> -<!ELEMENT method-param (#PCDATA)> - -<!-- -The method-params element contains a list of the fully-qualified Java -type names of the method parameters. - -Used in: method, query-method ---> -<!ELEMENT method-params (method-param*)> - -<!-- - -The method-permission element specifies that one or more security -roles are allowed to invoke one or more enterprise bean methods. The -method-permission element consists of an optional description, a list -of security role names or an indicator to state that the method is -unchecked for authorization, and a list of method elements. - -The security roles used in the method-permission element must be -defined in the security-role elements of the deployment descriptor, -and the methods must be methods defined in the enterprise bean's -component and/or home interfaces. - - -Used in: assembly-descriptor ---> -<!ELEMENT method-permission (description?, (role-name+|unchecked), method+)> - -<!-- -The multiplicity element describes the multiplicity of the role that -participates in a relation. - -The multiplicity element must be one of the two following: - - <multiplicity>One</multiplicity> - <multiplicity>Many</multiplicity> - -Used in: ejb-relationship-role ---> -<!ELEMENT multiplicity (#PCDATA)> - -<!-- -The persistence-type element specifies an entity bean's persistence -management type. - -The persistence-type element must be one of the two following: - - <persistence-type>Bean</persistence-type> - <persistence-type>Container</persistence-type> - -Used in: entity ---> -<!ELEMENT persistence-type (#PCDATA)> - -<!-- -The prim-key-class element contains the fully-qualified name of an -entity bean's primary key class. - -If the definition of the primary key class is deferred to deployment -time, the prim-key-class element should specify java.lang.Object. - -Used in: entity - -Examples: - - <prim-key-class>java.lang.String</prim-key-class> - - <prim-key-class>com.wombat.empl.EmployeeID</prim-key-class> - - <prim-key-class>java.lang.Object</prim-key-class> - ---> -<!ELEMENT prim-key-class (#PCDATA)> - -<!-- -The primkey-field element is used to specify the name of the primary -key field for an entity with container-managed persistence. - -The primkey-field must be one of the fields declared in the cmp-field -element, and the type of the field must be the same as the primary key -type. - -The primkey-field element is not used if the primary key maps to -multiple container-managed fields (i.e. the key is a compound key). In -this case, the fields of the primary key class must be public, and -their names must correspond to the field names of the entity bean -class that comprise the key. - -Used in: entity - -Example: - - <primkey-field>EmployeeId</primkey-field> - ---> -<!ELEMENT primkey-field (#PCDATA)> - -<!-- -The query element is used to specify a finder or select query. It -contains - - an optional description of the query - - the specification of the finder or select - method it is used by - - an optional specification of the result type mapping, if - the query is for a select method and entity objects are - returned. - - the EJB QL query string that defines the query. - -Queries that are expressible in EJB QL must use the ejb-ql element to -specify the query. If a query is not expressible in EJB QL, the -description element should be used to describe the semantics of the -query and the ejb-ql element should be empty. - -The result-type-mapping is an optional element. It can only be present -if the query-method specifies a select method that returns entity -objects. The default value for the result-type-mapping element is -"Local". - - -Used in: entity ---> -<!ELEMENT query (description?, query-method, result-type-mapping?, ejb-ql)> - -<!-- -The query-method element is used to specify the method for a finder or -select query. - -The method-name element specifies the name of a finder or select -method in the entity bean's implementation class. - -Each method-param must be defined for a query-method using the -method-params element. - -Used in: query - -Example: - -<query> - <description>Method finds large orders</description> - <query-method> - <method-name>findLargeOrders</method-name> - <method-params></method-params> - </query-method> - <ejb-ql>SELECT OBJECT(o) FROM Order o WHERE o.amount > 1000</ejb-ql> -</query> - ---> -<!ELEMENT query-method (method-name, method-params)> - -<!-- -The reentrant element specifies whether an entity bean is reentrant or -not. - -The reentrant element must be one of the two following: - - <reentrant>True</reentrant> - <reentrant>False</reentrant> - -Used in: entity ---> -<!ELEMENT reentrant (#PCDATA)> - -<!-- - -The relationship-role-source element designates the source of a role -that participates in a relationship. A relationship-role-source -element uniquely identifies an entity bean. - -Used in: ejb-relationship-role ---> -<!ELEMENT relationship-role-source (description?, ejb-name)> - -<!-- -The relationships element describes the relationships in which -entity beans with container-managed persistence participate. The -relationships element contains an optional description; and a list of -ejb-relation elements, which specify the container managed -relationships. - - -Used in: ejb-jar ---> -<!ELEMENT relationships (description?, ejb-relation+)> - -<!-- -The remote element contains the fully-qualified name of the enterprise -bean's remote interface. - -Used in: ejb-ref, entity, session - -Example: - -<remote>com.wombat.empl.EmployeeService</remote> ---> -<!ELEMENT remote (#PCDATA)> - -<!-- -The res-auth element specifies whether the enterprise bean code signs -on programmatically to the resource manager, or whether the Container -will sign on to the resource manager on behalf of the enterprise bean. In the -latter case, the Container uses information that is supplied by the -Deployer. - -The value of this element must be one of the two following: - - <res-auth>Application</res-auth> - <res-auth>Container</res-auth> - -Used in: resource-ref ---> -<!ELEMENT res-auth (#PCDATA)> - -<!-- -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 enterprise bean. - -Used in: resource-ref ---> -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-sharing-scope element specifies whether connections obtained -through the given resource manager connection factory reference can be -shared. The value of this element, if specified, must be one of the -two following: - - <res-sharing-scope>Shareable</res-sharing-scope> - <res-sharing-scope>Unshareable</res-sharing-scope> - -The default value is Shareable. - -Used in: resource-ref ---> -<!ELEMENT res-sharing-scope (#PCDATA)> - -<!-- -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. - -Used in: resource-ref ---> -<!ELEMENT res-type (#PCDATA)> - -<!-- -The resource-env-ref element contains a declaration of an enterprise bean's -reference to an administered object associated with a resource -in the enterprise bean's environment. It consists of an optional -description, the resource environment reference name, and an -indication of the resource environment reference type expected by -the enterprise bean code. - -Used in: entity, message-driven, session - -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> ---> -<!ELEMENT resource-env-ref (description?, resource-env-ref-name, - resource-env-ref-type)> - -<!-- -The resource-env-ref-name element specifies the name of a resource -environment reference; its value is the environment entry name used in -the enterprise bean code. The name is a JNDI name relative to the -java:comp/env context and must be unique within an enterprise bean. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-name (#PCDATA)> - -<!-- -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. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-type (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of an enterprise bean's -reference to an external resource. It consists of an optional -description, the resource manager connection factory reference name, -the indication of the resource manager connection factory type -expected by the enterprise bean code, the type of authentication -(Application or Container), and an optional specification of the -shareability of connections obtained from the resource (Shareable or -Unshareable). - -Used in: entity, message-driven, session - -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> ---> -<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth, - res-sharing-scope?)> - -<!-- - -The result-type-mapping element is used in the query element to specify -whether an abstract schema type returned by a query for a select method -is to be mapped to an EJBLocalObject or EJBObject type. - -The result-type-mapping element must be one of the following: - - <result-type-mapping>Local</result-type-mapping> - <result-type-mapping>Remote</result-type-mapping> - -Used in: query ---> -<!ELEMENT result-type-mapping (#PCDATA)> - -<!-- -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. - -Used in: security-role-ref ---> -<!ELEMENT role-link (#PCDATA)> - -<!-- -The role-name element contains the name of a security role. - -The name must conform to the lexical rules for an NMTOKEN. - -Used in: method-permission, run-as, security-role, security-role-ref ---> -<!ELEMENT role-name (#PCDATA)> - -<!-- -The run-as element specifies the run-as identity to be used for the -execution of the enterprise bean. It contains an optional description, and -the name of a security role. - -Used in: security-identity ---> -<!ELEMENT run-as (description?, role-name)> - -<!-- - -The security-identity element specifies whether the caller's -security identity is to be used for the execution of the methods of -the enterprise bean or whether a specific run-as identity is to be -used. It contains an optional description and a specification of the -security identity to be used. - -Used in: entity, message-driven, session ---> -<!ELEMENT security-identity (description?, (use-caller-identity|run-as))> - -<!-- -The security-role element contains the definition of a security -role. The definition consists of an optional description of the -security role, and the security role name. - -Used in: assembly-descriptor - -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> ---> -<!ELEMENT security-role (description?, role-name)> - -<!-- -The security-role-ref element contains the declaration of a security -role reference in the enterprise bean'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. - -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. - -Used in: entity, session - ---> -<!ELEMENT security-role-ref (description?, role-name, role-link?)> - -<!-- -The session element declares an session bean. The declaration consists -of: - - an optional description - - an optional display name - - an optional small icon file name - - an optional large icon file name - - a name assigned to the enterprise bean - in the deployment description - - the names of the session bean's remote home and - remote interfaces, if any - - the names of the session bean's local home and - local interfaces, if any - - the session bean's implementation class - - the session bean's state management type - - the session bean's transaction management type - - an optional declaration of the bean's environment entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local EJB references - - an optional declaration of the security role references - - an optional declaration of the security identity to be - used for the execution of the bean's methods - - an optional declaration of the bean's resource manager - connection factory references - - an optional declaration of the bean's resource environment - references. - -The elements that are optional are "optional" in the sense that they -are omitted when if lists represented by them are empty. - -Either both the local-home and the local elements or both the -home and the remote elements must be specified for the session bean. - -Used in: enterprise-beans ---> -<!ELEMENT session (description?, display-name?, small-icon?, -large-icon?, ejb-name, home?, remote?, local-home?, local?, -ejb-class, session-type, transaction-type, env-entry*, ejb-ref*, -ejb-local-ref*, security-role-ref*, security-identity?, resource-ref*, -resource-env-ref*)> - -<!-- -The session-type element describes whether the session bean is a -stateful session or stateless session. - -The session-type element must be one of the two following: - - <session-type>Stateful</session-type> - <session-type>Stateless</session-type> ---> -<!ELEMENT session-type (#PCDATA)> - -<!-- -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 enterprise bean's -ejb-jar file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: ejb-jar, entity, message-driven, session - -Example: - -<small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The subscription-durability element specifies whether a JMS topic -subscription is intended to be durable or nondurable. - -The subscription-durability element must be one of the two following: - - <subscription-durability>Durable</subscription-durability> - <subscription-durability>NonDurable</subscription-durability> - -Used in: message-driven-destination ---> -<!ELEMENT subscription-durability (#PCDATA)> - -<!-- -The trans-attribute element specifies how the container must manage -the transaction boundaries when delegating a method invocation to an -enterprise bean's business method. - -The value of trans-attribute must be one of the following: - - - <trans-attribute>NotSupported</trans-attribute> - <trans-attribute>Supports</trans-attribute> - <trans-attribute>Required</trans-attribute> - <trans-attribute>RequiresNew</trans-attribute> - <trans-attribute>Mandatory</trans-attribute> - <trans-attribute>Never</trans-attribute> - -Used in: container-transaction ---> -<!ELEMENT trans-attribute (#PCDATA)> - -<!-- -The transaction-type element specifies an enterprise bean's -transaction management type. - -The transaction-type element must be one of the two following: - - <transaction-type>Bean</transaction-type> - <transaction-type>Container</transaction-type> - -Used in: message-driven, session ---> -<!ELEMENT transaction-type (#PCDATA)> - -<!-- -The unchecked element specifies that a method is not checked for authorization -by the container prior to invocation of the method. - -Used in: method-permission ---> -<!ELEMENT unchecked EMPTY> - -<!-- - -The use-caller-identity element specifies that the caller's security -identity be used as the security identity for the execution of the -enterprise bean's methods. - -Used in: security-identity ---> -<!ELEMENT use-caller-identity EMPTY> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e., information beyond the standard deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tool-specific files to the -information in the standard deployment descriptor. - -Tools are not allowed to add the non-standard information into the -standard deployment descriptor. ---> - -<!ATTLIST abstract-schema-name id ID #IMPLIED> -<!ATTLIST acknowledge-mode id ID #IMPLIED> -<!ATTLIST assembly-descriptor id ID #IMPLIED> -<!ATTLIST cascade-delete id ID #IMPLIED> -<!ATTLIST cmp-field id ID #IMPLIED> -<!ATTLIST cmp-version id ID #IMPLIED> -<!ATTLIST cmr-field id ID #IMPLIED> -<!ATTLIST cmr-field-name id ID #IMPLIED> -<!ATTLIST cmr-field-type id ID #IMPLIED> -<!ATTLIST container-transaction id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST destination-type id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST ejb-class id ID #IMPLIED> -<!ATTLIST ejb-client-jar id ID #IMPLIED> -<!ATTLIST ejb-jar id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> -<!ATTLIST ejb-local-ref id ID #IMPLIED> -<!ATTLIST ejb-name id ID #IMPLIED> -<!ATTLIST ejb-ql id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST ejb-relation id ID #IMPLIED> -<!ATTLIST ejb-relation-name id ID #IMPLIED> -<!ATTLIST ejb-relationship-role id ID #IMPLIED> -<!ATTLIST ejb-relationship-role-name id ID #IMPLIED> -<!ATTLIST enterprise-beans id ID #IMPLIED> -<!ATTLIST entity id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST exclude-list id ID #IMPLIED> -<!ATTLIST field-name id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST local id ID #IMPLIED> -<!ATTLIST local-home id ID #IMPLIED> -<!ATTLIST message-driven id ID #IMPLIED> -<!ATTLIST message-driven-destination id ID #IMPLIED> -<!ATTLIST message-selector id ID #IMPLIED> -<!ATTLIST method id ID #IMPLIED> -<!ATTLIST method-intf id ID #IMPLIED> -<!ATTLIST method-name id ID #IMPLIED> -<!ATTLIST method-param id ID #IMPLIED> -<!ATTLIST method-params id ID #IMPLIED> -<!ATTLIST method-permission id ID #IMPLIED> -<!ATTLIST multiplicity id ID #IMPLIED> -<!ATTLIST persistence-type id ID #IMPLIED> -<!ATTLIST prim-key-class id ID #IMPLIED> -<!ATTLIST primkey-field id ID #IMPLIED> -<!ATTLIST query id ID #IMPLIED> -<!ATTLIST query-method id ID #IMPLIED> -<!ATTLIST reentrant id ID #IMPLIED> -<!ATTLIST relationship-role-source id ID #IMPLIED> -<!ATTLIST relationships id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-sharing-scope id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST resource-env-ref id ID #IMPLIED> -<!ATTLIST resource-env-ref-name id ID #IMPLIED> -<!ATTLIST resource-env-ref-type id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST result-type-mapping id ID #IMPLIED> -<!ATTLIST role-link id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST run-as id ID #IMPLIED> -<!ATTLIST security-identity id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST security-role-ref id ID #IMPLIED> -<!ATTLIST session id ID #IMPLIED> -<!ATTLIST session-type id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST subscription-durability id ID #IMPLIED> -<!ATTLIST trans-attribute id ID #IMPLIED> -<!ATTLIST transaction-type id ID #IMPLIED> -<!ATTLIST unchecked id ID #IMPLIED> -<!ATTLIST use-caller-identity id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_1.xsd deleted file mode 100644 index 419426b7ad..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_2_1.xsd +++ /dev/null @@ -1,2208 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="2.1"> - <xsd:annotation> - <xsd:documentation> - @(#)ejb-jar_2_1.xsds 1.23 08/01/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the EJB 2.1 deployment descriptor. - The deployment descriptor must be named "META-INF/ejb-jar.xml" in - the EJB's jar file. All EJB deployment descriptors must indicate - the ejb-jar schema by using the J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and by indicating the version of the schema by - using the version element as shown below: - - <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" - version="2.1"> - ... - </ejb-jar> - - The instance documents may indicate the published version of - the schema using the xsi:schemaLocation attribute for the - J2EE namespace with the following location: - - http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="ejb-jar" type="j2ee:ejb-jarType"> - <xsd:annotation> - <xsd:documentation> - - This is the root of the ejb-jar deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - - <xsd:key name="ejb-name-key"> - <xsd:annotation> - <xsd:documentation> - - The ejb-name element contains the name of an enterprise - bean. The name must be unique within the ejb-jar file. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:enterprise-beans/*"/> - <xsd:field xpath="j2ee:ejb-name"/> - </xsd:key> - - <xsd:keyref name="ejb-name-references" - refer="j2ee:ejb-name-key"> - <xsd:annotation> - <xsd:documentation> - - The keyref indicates the references from - relationship-role-source must be to a specific ejb-name - defined within the scope of enterprise-beans element. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector - xpath=".//j2ee:ejb-relationship-role/j2ee:relationship-role-source"/> - <xsd:field - xpath="j2ee:ejb-name"/> - </xsd:keyref> - - <xsd:key name="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="j2ee:assembly-descriptor/j2ee:security-role"/> - <xsd:field xpath="j2ee:role-name"/> - </xsd:key> - - <xsd:keyref name="role-name-references" - refer="j2ee: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="j2ee:enterprise-beans/*/j2ee:security-role-ref"/> - <xsd:field xpath="j2ee:role-link"/> - </xsd:keyref> - </xsd:element> - - -<!-- **************************************************** --> - - <xsd:complexType name="activation-config-propertyType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-propertyType contains a name/value - configuration property pair for a message-driven bean. - - The properties that are recognized for a particular - message-driven bean are determined by the messaging type. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="activation-config-property-name" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-property-name element contains - the name for an activation configuration property of - a message-driven bean. - - For JMS message-driven beans, the following property - names are recognized: acknowledgeMode, - messageSelector, destinationType, subscriptionDurability - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="activation-config-property-value" - type="j2ee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-property-value element - contains the value for an activation configuration - property of a message-driven bean. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="activation-configType"> - <xsd:annotation> - <xsd:documentation> - - The activation-configType defines information about the - expected configuration properties of the message-driven bean - in its operational environment. This may include information - about message acknowledgement, message selector, expected - destination type, etc. - - The configuration information is expressed in terms of - name/value configuration properties. - - The properties that are recognized for a particular - message-driven bean are determined by the messaging type. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="activation-config-property" - type="j2ee:activation-config-propertyType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="assembly-descriptorType"> - <xsd:annotation> - <xsd:documentation> - - The assembly-descriptorType defines - application-assembly information. - - The application-assembly information consists of the - following parts: the definition of security roles, the - definition of method permissions, the definition of - transaction attributes for enterprise beans with - container-managed transaction demarcation and a list of - methods to be excluded from being invoked. - - All the parts are optional in the sense that they are - omitted if the lists represented by them are empty. - - Providing an assembly-descriptor in the deployment - descriptor is optional for the ejb-jar file producer. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="security-role" - type="j2ee:security-roleType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method-permission" - type="j2ee:method-permissionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="container-transaction" - type="j2ee:container-transactionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="message-destination" - type="j2ee:message-destinationType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="exclude-list" - type="j2ee:exclude-listType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmp-fieldType"> - <xsd:annotation> - <xsd:documentation> - - The cmp-fieldType describes a container-managed field. The - cmp-fieldType contains an optional description of the field, - and the name of the field. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="field-name" - type="j2ee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The field-name element specifies the name of a - container managed field. - - The name of the cmp-field of an entity bean with - cmp-version 2.x must begin with a lowercase - letter. This field is accessed by methods whose - names consists of the name of the field specified by - field-name in which the first letter is uppercased, - prefixed by "get" or "set". - - The name of the cmp-field of an entity bean with - cmp-version 1.x must denote a public field of the - enterprise bean class or one of its superclasses. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmp-versionType"> - <xsd:annotation> - <xsd:documentation> - - The cmp-versionType specifies the version of an entity bean - with container-managed persistence. It is used by - cmp-version elements. - - The value must be one of the two following: - - 1.x - 2.x - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="1.x"/> - <xsd:enumeration value="2.x"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmr-field-typeType"> - <xsd:annotation> - <xsd:documentation> - - The cmr-field-type element specifies the class of a - collection-valued logical relationship field in the entity - bean class. The value of an element using cmr-field-typeType - must be either: java.util.Collection or java.util.Set. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="java.util.Collection"/> - <xsd:enumeration value="java.util.Set"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmr-fieldType"> - <xsd:annotation> - <xsd:documentation> - - The cmr-fieldType describes the bean provider's view of - a relationship. It consists of an optional description, and - the name and the class type of a field in the source of a - role of a relationship. The cmr-field-name element - corresponds to the name used for the get and set accessor - methods for the relationship. The cmr-field-type element is - used only for collection-valued cmr-fields. It specifies the - type of the collection that is used. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="cmr-field-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The cmr-field-name element specifies the name of a - logical relationship field in the entity bean - class. The name of the cmr-field must begin with a - lowercase letter. This field is accessed by methods - whose names consist of the name of the field - specified by cmr-field-name in which the first - letter is uppercased, prefixed by "get" or "set". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmr-field-type" - type="j2ee:cmr-field-typeType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="container-transactionType"> - <xsd:annotation> - <xsd:documentation> - - The container-transactionType specifies how the container - must manage transaction scopes for the enterprise bean's - method invocations. It defines an optional description, a - list of method elements, and a transaction attribute. The - transaction attribute is to be applied to all the specified - methods. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method" - type="j2ee:methodType" - maxOccurs="unbounded"/> - <xsd:element name="trans-attribute" - type="j2ee:trans-attributeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-classType contains the fully-qualified name of the - enterprise bean's class. It is used by ejb-class elements. - - Example: - - <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-jarType"> - <xsd:annotation> - <xsd:documentation> - - The ejb-jarType defines the root element of the EJB - deployment descriptor. It contains - - - an optional description of the ejb-jar file - - an optional display name - - an optional icon that contains a small and a large - icon file name - - mandatory structural information about all included - enterprise beans - - a descriptor for container managed relationships, - if any - - an optional application-assembly descriptor - - an optional name of an ejb-client-jar file for the - ejb-jar. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="enterprise-beans" - type="j2ee:enterprise-beansType"/> - <xsd:element name="relationships" - type="j2ee:relationshipsType" - minOccurs="0"> - <xsd:unique name="relationship-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relation-name contains the name of a - relation. The name must be unique within - relationships. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-relation"/> - <xsd:field xpath="j2ee:ejb-relation-name"/> - </xsd:unique> - </xsd:element> - <xsd:element name="assembly-descriptor" - type="j2ee:assembly-descriptorType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Providing an assembly-descriptor in the deployment - descriptor is optional for the ejb-jar file - producer. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-client-jar" - type="j2ee:pathType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The optional ejb-client-jar element specifies a JAR - file that contains the class files necessary for a - client program to access the - enterprise beans in the ejb-jar file. - - Example: - - <ejb-client-jar>employee_service_client.jar - </ejb-client-jar> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="2.1" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The version specifies the version of the - EJB specification that the instance document must - comply with. This information enables deployment tools - to validate a particular EJB Deployment - Descriptor with respect to a specific version of the EJB - schema. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-nameType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-nameType specifies an enterprise bean's name. It is - used by ejb-name elements. This name is assigned by the - ejb-jar file producer to name the enterprise bean in the - ejb-jar file's deployment descriptor. The name must be - unique among the names of the enterprise beans in the same - ejb-jar file. - - There is no architected relationship between the used - ejb-name in the deployment descriptor and the JNDI name that - the Deployer will assign to the enterprise bean's home. - - The name for an entity bean must conform to the lexical - rules for an NMTOKEN. - - Example: - - <ejb-name>EmployeeService</ejb-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:xsdNMTOKENType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-relationType"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationType describes a relationship between two - entity beans with container-managed persistence. It is used - by ejb-relation elements. It contains a description; an - optional ejb-relation-name element; and exactly two - relationship role declarations, defined by the - ejb-relationship-role elements. The name of the - relationship, if specified, is unique within the ejb-jar - file. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relation-name" - type="j2ee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relation-name element provides a unique name - within the ejb-jar file for a relationship. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-relationship-role" - type="j2ee:ejb-relationship-roleType"/> - <xsd:element name="ejb-relationship-role" - type="j2ee:ejb-relationship-roleType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-relationship-roleType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-relationship-roleType describes a role within a - relationship. There are two roles in each relationship. - - The ejb-relationship-roleType contains an optional - description; an optional name for the relationship role; a - specification of the multiplicity of the role; an optional - specification of cascade-delete functionality for the role; - the role source; and a declaration of the cmr-field, if any, - by means of which the other side of the relationship is - accessed from the perspective of the role source. - - The multiplicity and role-source element are mandatory. - - The relationship-role-source element designates an entity - bean by means of an ejb-name element. For bidirectional - relationships, both roles of a relationship must declare a - relationship-role-source element that specifies a cmr-field - in terms of which the relationship is accessed. The lack of - a cmr-field element in an ejb-relationship-role specifies - that the relationship is unidirectional in navigability and - the entity bean that participates in the relationship is - "not aware" of the relationship. - - Example: - - <ejb-relation> - <ejb-relation-name>Product-LineItem</ejb-relation-name> - <ejb-relationship-role> - <ejb-relationship-role-name>product-has-lineitems - </ejb-relationship-role-name> - <multiplicity>One</multiplicity> - <relationship-role-source> - <ejb-name>ProductEJB</ejb-name> - </relationship-role-source> - </ejb-relationship-role> - </ejb-relation> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relationship-role-name" - type="j2ee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationship-role-name element defines a - name for a role that is unique within an - ejb-relation. Different relationships can use the - same name for a role. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="multiplicity" - type="j2ee:multiplicityType"/> - <xsd:element name="cascade-delete" - type="j2ee:emptyType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The cascade-delete element specifies that, within a - particular relationship, the lifetime of one or more - entity beans is dependent upon the lifetime of - another entity bean. The cascade-delete element can - only be specified for an ejb-relationship-role - element contained in an ejb-relation element in - which the other ejb-relationship-role - element specifies a multiplicity of One. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="relationship-role-source" - type="j2ee:relationship-role-sourceType"/> - <xsd:element name="cmr-field" - type="j2ee:cmr-fieldType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="enterprise-beansType"> - <xsd:annotation> - <xsd:documentation> - - The enterprise-beansType declares one or more enterprise - beans. Each bean can be a session, entity or message-driven - bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:choice maxOccurs="unbounded"> - <xsd:element name="session" - type="j2ee:session-beanType"> - <xsd:unique name="session-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-local-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - It is recommended that name is prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-env-ref"/> - <xsd:field xpath="j2ee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:message-destination-ref"/> - <xsd:field xpath="j2ee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-ref"/> - <xsd:field xpath="j2ee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:env-entry"/> - <xsd:field xpath="j2ee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - <xsd:element name="entity" - type="j2ee:entity-beanType"> - <xsd:unique name="entity-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-local-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - It is recommended that name is prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-env-ref"/> - <xsd:field xpath="j2ee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:message-destination-ref"/> - <xsd:field xpath="j2ee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-ref"/> - <xsd:field xpath="j2ee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:env-entry"/> - <xsd:field xpath="j2ee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - <xsd:element name="message-driven" - type="j2ee:message-driven-beanType"> - <xsd:unique name="messaged-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-local-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - It is recommended that name is prefixed with "ejb/". - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:ejb-ref"/> - <xsd:field xpath="j2ee:ejb-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-env-ref"/> - <xsd:field xpath="j2ee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:message-destination-ref"/> - <xsd:field xpath="j2ee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:resource-ref"/> - <xsd:field xpath="j2ee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:env-entry"/> - <xsd:field xpath="j2ee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - </xsd:choice> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="entity-beanType"> - <xsd:annotation> - <xsd:documentation> - - The entity-beanType declares an entity bean. The declaration - consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name - - a unique name assigned to the enterprise bean - in the deployment descriptor - - the names of the entity bean's remote home - and remote interfaces, if any - - the names of the entity bean's local home and local - interfaces, if any - - the entity bean's implementation class - - the entity bean's persistence management type - - the entity bean's primary key class name - - an indication of the entity bean's reentrancy - - an optional specification of the - entity bean's cmp-version - - an optional specification of the entity bean's - abstract schema name - - an optional list of container-managed fields - - an optional specification of the primary key - field - - an optional declaration of the bean's environment - entries - - an optional declaration of the bean's EJB - references - - an optional declaration of the bean's local - EJB references - - an optional declaration of the bean's web - service references - - an optional declaration of the security role - references - - an optional declaration of the security identity - to be used for the execution of the bean's methods - - an optional declaration of the bean's - resource manager connection factory references - - an optional declaration of the bean's - resource environment references - - an optional declaration of the bean's message - destination references - - an optional set of query declarations - for finder and select methods for an entity - bean with cmp-version 2.x. - - The optional abstract-schema-name element must be specified - for an entity bean with container-managed persistence and - cmp-version 2.x. - - The optional primkey-field may be present in the descriptor - if the entity's persistence-type is Container. - - The optional cmp-version element may be present in the - descriptor if the entity's persistence-type is Container. If - the persistence-type is Container and the cmp-version - element is not specified, its value defaults to 2.x. - - The optional home and remote elements must be specified if - the entity bean cmp-version is 1.x. - - The optional home and remote elements must be specified if - the entity bean has a remote home and remote interface. - - The optional local-home and local elements must be specified - if the entity bean has a local home and local interface. - - Either both the local-home and the local elements or both - the home and the remote elements must be specified. - - The optional query elements must be present if the - persistence-type is Container and the cmp-version is 2.x and - query methods other than findByPrimaryKey have been defined - for the entity bean. - - The other elements that are optional are "optional" in the - sense that they are omitted if the lists represented by them - are empty. - - At least one cmp-field element must be present in the - descriptor if the entity's persistence-type is Container and - the cmp-version is 1.x, and none must not be present if the - entity's persistence-type is Bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="j2ee:ejb-nameType"/> - <xsd:element name="home" - type="j2ee:homeType" - minOccurs="0"/> - <xsd:element name="remote" - type="j2ee:remoteType" - minOccurs="0"/> - <xsd:element name="local-home" - type="j2ee:local-homeType" - minOccurs="0"/> - <xsd:element name="local" - type="j2ee:localType" - minOccurs="0"/> - <xsd:element name="ejb-class" - type="j2ee:ejb-classType"/> - <xsd:element name="persistence-type" - type="j2ee:persistence-typeType"/> - <xsd:element name="prim-key-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The prim-key-class element contains the - fully-qualified name of an - entity bean's primary key class. - - If the definition of the primary key class is - deferred to deployment time, the prim-key-class - element should specify java.lang.Object. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="reentrant" - type="j2ee:true-falseType"> - <xsd:annotation> - <xsd:documentation> - - The reentrant element specifies whether an entity - bean is reentrant or not. - - The reentrant element must be one of the two - following: true or false - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmp-version" - type="j2ee:cmp-versionType" - minOccurs="0"/> - <xsd:element name="abstract-schema-name" - type="j2ee:java-identifierType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The abstract-schema-name element specifies the name - of the abstract schema type of an entity bean with - cmp-version 2.x. It is used in EJB QL queries. - - For example, the abstract-schema-name for an entity - bean whose local interface is - com.acme.commerce.Order might be Order. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmp-field" - type="j2ee:cmp-fieldType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="primkey-field" - type="j2ee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The primkey-field element is used to specify the - name of the primary key field for an entity with - container-managed persistence. - - The primkey-field must be one of the fields declared - in the cmp-field element, and the type of the field - must be the same as the primary key type. - - The primkey-field element is not used if the primary - key maps to multiple container-managed fields - (i.e. the key is a compound key). In this case, the - fields of the primary key class must be public, and - their names must correspond to the field names of - the entity bean class that comprise the key. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/> - <xsd:element name="security-role-ref" - type="j2ee:security-role-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="security-identity" - type="j2ee:security-identityType" - minOccurs="0"/> - <xsd:element name="query" - type="j2ee:queryType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="exclude-listType"> - <xsd:annotation> - <xsd:documentation> - - The exclude-listType specifies one or more methods which - the Assembler marks to be uncallable. - - If the method permission relation contains methods that are - in the exclude list, the Deployer should consider those - methods to be uncallable. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method" - type="j2ee:methodType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-driven-beanType"> - <xsd:annotation> - <xsd:documentation> - - The message-driven element declares a message-driven - bean. The declaration consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name. - - a name assigned to the enterprise bean in - the deployment descriptor - - the message-driven bean's implementation class - - an optional declaration of the bean's messaging - type - - the message-driven bean's transaction management type - - an optional declaration of the bean's - message-destination-type - - an optional declaration of the bean's - message-destination-link - - an optional declaration of the message-driven bean's - activation configuration properties - - an optional declaration of the bean's environment - entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local EJB - references - - an optional declaration of the bean's web service - references - - an optional declaration of the security - identity to be used for the execution of the bean's - methods - - an optional declaration of the bean's - resource manager connection factory - references - - an optional declaration of the bean's resource - environment references. - - an optional declaration of the bean's message - destination references - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="j2ee:ejb-nameType"/> - <xsd:element name="ejb-class" - type="j2ee:ejb-classType"/> - <xsd:element name="messaging-type" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The messaging-type element specifies the message - listener interface of the message-driven bean. If - the messaging-type element is not specified, it is - assumed to be javax.jms.MessageListener. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="transaction-type" - type="j2ee:transaction-typeType"/> - <xsd:element name="message-destination-type" - type="j2ee:message-destination-typeType" - minOccurs="0"/> - <xsd:element name="message-destination-link" - type="j2ee:message-destination-linkType" - minOccurs="0"/> - <xsd:element name="activation-config" - type="j2ee:activation-configType" - minOccurs="0"/> - <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/> - <xsd:element name="security-identity" - type="j2ee:security-identityType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-intfType"> - - <xsd:annotation> - <xsd:documentation> - - The method-intf element allows a method element to - differentiate between the methods with the same name and - signature that are multiply defined across the home and - component interfaces (e.g, in both an enterprise bean's - remote and local interfaces or in both an enterprise bean's - home and remote interfaces, etc.); the component and web - service endpoint interfaces, and so on. - - The method-intf element must be one of the following: - - Home - Remote - LocalHome - Local - ServiceEndpoint - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="Home"/> - <xsd:enumeration value="Remote"/> - <xsd:enumeration value="LocalHome"/> - <xsd:enumeration value="Local"/> - <xsd:enumeration value="ServiceEndpoint"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-nameType"> - <xsd:annotation> - <xsd:documentation> - - The method-nameType contains a name of an enterprise - bean method or the asterisk (*) character. The asterisk is - used when the element denotes all the methods of an - enterprise bean's client view interfaces. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-paramsType"> - <xsd:annotation> - <xsd:documentation> - - The method-paramsType defines a list of the - fully-qualified Java type names of the method parameters. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="method-param" - type="j2ee:java-typeType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The method-param element contains a primitive - or a fully-qualified Java type name of a method - parameter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-permissionType"> - <xsd:annotation> - <xsd:documentation> - - The method-permissionType specifies that one or more - security roles are allowed to invoke one or more enterprise - bean methods. The method-permissionType consists of an - optional description, a list of security role names or an - indicator to state that the method is unchecked for - authorization, and a list of method elements. - - The security roles used in the method-permissionType - must be defined in the security-role elements of the - deployment descriptor, and the methods must be methods - defined in the enterprise bean's home, component and/or web - service endpoint interfaces. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="role-name" - type="j2ee:role-nameType" - maxOccurs="unbounded"/> - <xsd:element name="unchecked" - type="j2ee:emptyType"> - <xsd:annotation> - <xsd:documentation> - - The unchecked element specifies that a method is - not checked for authorization by the container - prior to invocation of the method. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - <xsd:element name="method" - type="j2ee:methodType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="methodType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The methodType is used to denote a method of an enterprise - bean's home, component, and/or web service endpoint - interface, or, in the case of a message-driven bean, the - bean's message listener method, or a set of such - methods. The ejb-name element must be the name of one of the - enterprise beans declared in the deployment descriptor; the - optional method-intf element allows to distinguish between a - method with the same signature that is multiply defined - across the home, component, and/or web service endpoint - interfaces; the method-name element specifies the method - name; and the optional method-params elements identify a - single method among multiple methods with an overloaded - method name. - - There are three possible styles of using methodType element - within a method element: - - 1. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>*</method-name> - </method> - - This style is used to refer to all the methods of the - specified enterprise bean's home, component, and/or web - service endpoint interfaces. - - 2. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - </method> - - This style is used to refer to the specified method of - the specified enterprise bean. If there are multiple - methods with the same overloaded name, the element of - this style refers to all the methods with the overloaded - name. - - 3. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - <method-params> - <method-param>PARAM-1</method-param> - <method-param>PARAM-2</method-param> - ... - <method-param>PARAM-n</method-param> - </method-params> - </method> - - This style is used to refer to a single method within a - set of methods with an overloaded name. PARAM-1 through - PARAM-n are the fully-qualified Java types of the - method's input parameters (if the method has no input - arguments, the method-params element contains no - method-param elements). Arrays are specified by the - array element's type, followed by one or more pair of - square brackets (e.g. int[][]). If there are multiple - methods with the same overloaded name, this style refers - to all of the overloaded methods. - - Examples: - - Style 1: The following method element refers to all the - methods of the EmployeeService bean's home, component, - and/or web service endpoint interfaces: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>*</method-name> - </method> - - Style 2: The following method element refers to all the - create methods of the EmployeeService bean's home - interface(s). - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - </method> - - Style 3: The following method element refers to the - create(String firstName, String LastName) method of the - EmployeeService bean's home interface(s). - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - The following example illustrates a Style 3 element with - more complex parameter types. The method - foobar(char s, int i, int[] iar, mypackage.MyClass mycl, - mypackage.MyClass[][] myclaar) would be specified as: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>foobar</method-name> - <method-params> - <method-param>char</method-param> - <method-param>int</method-param> - <method-param>int[]</method-param> - <method-param>mypackage.MyClass</method-param> - <method-param>mypackage.MyClass[][]</method-param> - </method-params> - </method> - - The optional method-intf element can be used when it becomes - necessary to differentiate between a method that is multiply - defined across the enterprise bean's home, component, and/or - web service endpoint interfaces with the same name and - signature. - - For example, the method element - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Remote</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - can be used to differentiate the create(String, String) - method defined in the remote interface from the - create(String, String) method defined in the remote home - interface, which would be defined as - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - and the create method that is defined in the local home - interface which would be defined as - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>LocalHome</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - The method-intf element can be used with all th ree Styles - of the method element usage. For example, the following - method element example could be used to refer to all the - methods of the EmployeeService bean's remote home interface. - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>*</method-name> - </method> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-name" - type="j2ee:ejb-nameType"/> - <xsd:element name="method-intf" - type="j2ee:method-intfType" - minOccurs="0"> - </xsd:element> - <xsd:element name="method-name" - type="j2ee:method-nameType"/> - <xsd:element name="method-params" - type="j2ee:method-paramsType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="multiplicityType"> - <xsd:annotation> - <xsd:documentation> - - The multiplicityType describes the multiplicity of the - role that participates in a relation. - - The value must be one of the two following: - - One - Many - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="One"/> - <xsd:enumeration value="Many"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="persistence-typeType"> - <xsd:annotation> - <xsd:documentation> - - The persistence-typeType specifies an entity bean's persistence - management type. - - The persistence-type element must be one of the two following: - - Bean - Container - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="Bean"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="query-methodType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The query-method specifies the method for a finder or select - query. - - The method-name element specifies the name of a finder or select - method in the entity bean's implementation class. - - Each method-param must be defined for a query-method using the - method-params element. - - It is used by the query-method element. - - Example: - - <query> - <description>Method finds large orders</description> - <query-method> - <method-name>findLargeOrders</method-name> - <method-params></method-params> - </query-method> - <ejb-ql> - SELECT OBJECT(o) FROM Order o - WHERE o.amount > 1000 - </ejb-ql> - </query> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="method-name" - type="j2ee:method-nameType"/> - <xsd:element name="method-params" - type="j2ee:method-paramsType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="queryType"> - <xsd:annotation> - <xsd:documentation> - - The queryType defines a finder or select - query. It contains - - an optional description of the query - - the specification of the finder or select - method it is used by - - an optional specification of the result type - mapping, if the query is for a select method - and entity objects are returned. - - the EJB QL query string that defines the query. - - Queries that are expressible in EJB QL must use the ejb-ql - element to specify the query. If a query is not expressible - in EJB QL, the description element should be used to - describe the semantics of the query and the ejb-ql element - should be empty. - - The result-type-mapping is an optional element. It can only - be present if the query-method specifies a select method - that returns entity objects. The default value for the - result-type-mapping element is "Local". - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" minOccurs="0"/> - <xsd:element name="query-method" - type="j2ee:query-methodType"/> - <xsd:element name="result-type-mapping" - type="j2ee:result-type-mappingType" - minOccurs="0"/> - <xsd:element name="ejb-ql" - type="j2ee:xsdStringType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="relationship-role-sourceType"> - <xsd:annotation> - <xsd:documentation> - - The relationship-role-sourceType designates the source of a - role that participates in a relationship. A - relationship-role-sourceType is used by - relationship-role-source elements to uniquely identify an - entity bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-name" - type="j2ee:ejb-nameType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="relationshipsType"> - <xsd:annotation> - <xsd:documentation> - - The relationshipsType describes the relationships in - which entity beans with container-managed persistence - participate. The relationshipsType contains an optional - description; and a list of ejb-relation elements, which - specify the container managed relationships. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relation" - type="j2ee:ejb-relationType" - maxOccurs="unbounded"> - - <xsd:unique name="role-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationship-role-name contains the name of a - relationship role. The name must be unique within - a relationship, but can be reused in different - relationships. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector - xpath=".//j2ee:ejb-relationship-role-name"/> - <xsd:field - xpath="."/> - </xsd:unique> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="result-type-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The result-type-mappingType is used in the query element to - specify whether an abstract schema type returned by a query - for a select method is to be mapped to an EJBLocalObject or - EJBObject type. - - The value must be one of the following: - - Local - Remote - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="Local"/> - <xsd:enumeration value="Remote"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-identityType"> - <xsd:annotation> - <xsd:documentation> - - The security-identityType specifies whether the caller's - security identity is to be used for the execution of the - methods of the enterprise bean or whether a specific run-as - identity is to be used. It contains an optional description - and a specification of the security identity to be used. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="use-caller-identity" - type="j2ee:emptyType"> - <xsd:annotation> - <xsd:documentation> - - The use-caller-identity element specifies that - the caller's security identity be used as the - security identity for the execution of the - enterprise bean's methods. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="run-as" - type="j2ee:run-asType"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-beanType"> - <xsd:annotation> - <xsd:documentation> - - The session-beanType declares an session bean. The - declaration consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name - - a name assigned to the enterprise bean - in the deployment description - - the names of the session bean's remote home and - remote interfaces, if any - - the names of the session bean's local home and - local interfaces, if any - - the name of the session bean's web service endpoint - interface, if any - - the session bean's implementation class - - the session bean's state management type - - the session bean's transaction management type - - an optional declaration of the bean's - environment entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local - EJB references - - an optional declaration of the bean's web - service references - - an optional declaration of the security role - references - - an optional declaration of the security identity - to be used for the execution of the bean's methods - - an optional declaration of the bean's resource - manager connection factory references - - an optional declaration of the bean's resource - environment references. - - an optional declaration of the bean's message - destination references - - The elements that are optional are "optional" in the sense - that they are omitted when if lists represented by them are - empty. - - Either both the local-home and the local elements or both - the home and the remote elements must be specified for the - session bean. - - The service-endpoint element may only be specified if the - bean is a stateless session bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="j2ee:ejb-nameType"/> - <xsd:element name="home" - type="j2ee:homeType" - minOccurs="0"/> - <xsd:element name="remote" - type="j2ee:remoteType" - minOccurs="0"/> - <xsd:element name="local-home" - type="j2ee:local-homeType" - minOccurs="0"/> - <xsd:element name="local" - type="j2ee:localType" - minOccurs="0"/> - <xsd:element name="service-endpoint" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The service-endpoint element contains the - fully-qualified name of the enterprise bean's web - service endpoint interface. The service-endpoint - element may only be specified for a stateless - session bean. The specified interface must be a - valid JAX-RPC service endpoint interface. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-class" - type="j2ee:ejb-classType"/> - <xsd:element name="session-type" - type="j2ee:session-typeType"/> - <xsd:element name="transaction-type" - type="j2ee:transaction-typeType"/> - <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/> - <xsd:element name="security-role-ref" - type="j2ee:security-role-refType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="security-identity" - type="j2ee:security-identityType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-typeType"> - <xsd:annotation> - <xsd:documentation> - - The session-typeType describes whether the session bean is a - stateful session or stateless session. It is used by - session-type elements. - - The value must be one of the two following: - - Stateful - Stateless - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="Stateful"/> - <xsd:enumeration value="Stateless"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="trans-attributeType"> - <xsd:annotation> - <xsd:documentation> - - The trans-attributeType specifies how the container must - manage the transaction boundaries when delegating a method - invocation to an enterprise bean's business method. - - The value must be one of the following: - - NotSupported - Supports - Required - RequiresNew - Mandatory - Never - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="NotSupported"/> - <xsd:enumeration value="Supports"/> - <xsd:enumeration value="Required"/> - <xsd:enumeration value="RequiresNew"/> - <xsd:enumeration value="Mandatory"/> - <xsd:enumeration value="Never"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="transaction-typeType"> - <xsd:annotation> - <xsd:documentation> - - The transaction-typeType specifies an enterprise bean's - transaction management type. - - The transaction-type must be one of the two following: - - Bean - Container - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="Bean"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_3_0.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_3_0.xsd deleted file mode 100644 index 48282913a4..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/ejb-jar_3_0.xsd +++ /dev/null @@ -1,2706 +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="3.0"> - <xsd:annotation> - <xsd:documentation> - @(#)ejb-jar_3_0.xsds 1.51 02/23/06 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003-2006 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 EJB 3.0 deployment descriptor. - The deployment descriptor must be named "META-INF/ejb-jar.xml" in - the EJB's jar file. All EJB deployment descriptors must indicate - the ejb-jar 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: - - <ejb-jar 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/ejb-jar_3_0.xsd" - version="3.0"> - ... - </ejb-jar> - - The instance documents may indicate the published version of - the schema using the xsi:schemaLocation attribute for the - Java EE namespace with the following location: - - http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.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="ejb-jar" type="javaee:ejb-jarType"> - <xsd:annotation> - <xsd:documentation> - - This is the root of the ejb-jar deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - - <xsd:key name="ejb-name-key"> - <xsd:annotation> - <xsd:documentation> - - The ejb-name element contains the name of an enterprise - bean. The name must be unique within the ejb-jar file. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:enterprise-beans/*"/> - <xsd:field xpath="javaee:ejb-name"/> - </xsd:key> - - <xsd:keyref name="ejb-name-references" - refer="javaee:ejb-name-key"> - <xsd:annotation> - <xsd:documentation> - - The keyref indicates the references from - relationship-role-source must be to a specific ejb-name - defined within the scope of enterprise-beans element. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector -xpath=".//javaee:ejb-relationship-role/javaee:relationship-role-source"/> - <xsd:field - xpath="javaee:ejb-name"/> - </xsd:keyref> - - <xsd:key name="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:assembly-descriptor/javaee:security-role"/> - <xsd:field xpath="javaee:role-name"/> - </xsd:key> - - <xsd:keyref name="role-name-references" - refer="javaee: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:enterprise-beans/*/javaee:security-role-ref"/> - <xsd:field xpath="javaee:role-link"/> - </xsd:keyref> - </xsd:element> - - -<!-- **************************************************** --> - - <xsd:complexType name="activation-config-propertyType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-propertyType contains a name/value - configuration property pair for a message-driven bean. - - The properties that are recognized for a particular - message-driven bean are determined by the messaging type. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="activation-config-property-name" - type="javaee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-property-name element contains - the name for an activation configuration property of - a message-driven bean. - - For JMS message-driven beans, the following property - names are recognized: acknowledgeMode, - messageSelector, destinationType, subscriptionDurability - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="activation-config-property-value" - type="javaee:xsdStringType"> - <xsd:annotation> - <xsd:documentation> - - The activation-config-property-value element - contains the value for an activation configuration - property of a message-driven bean. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="activation-configType"> - <xsd:annotation> - <xsd:documentation> - - The activation-configType defines information about the - expected configuration properties of the message-driven bean - in its operational environment. This may include information - about message acknowledgement, message selector, expected - destination type, etc. - - The configuration information is expressed in terms of - name/value configuration properties. - - The properties that are recognized for a particular - message-driven bean are determined by the messaging type. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="activation-config-property" - type="javaee:activation-config-propertyType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="application-exceptionType"> - <xsd:annotation> - <xsd:documentation> - - The application-exceptionType declares an application - exception. The declaration consists of: - - - the exception class. When the container receives - an exception of this type, it is required to - forward this exception as an applcation exception - to the client regardless of whether it is a checked - or unchecked exception. - - an optional rollback element. If this element is - set to true, the container must rollback the current - transaction before forwarding the exception to the - client. If not specified, it defaults to false. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="exception-class" - type="javaee:fully-qualified-classType"/> - <xsd:element name="rollback" - type="javaee:true-falseType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="around-invokeType"> - <xsd:annotation> - <xsd:documentation> - - The around-invoke type specifies a method on a - class to be called during the around invoke portion of an - ejb invocation. Note that each class may have only one - around invoke method and that the method may not be - overloaded. - - If the class element is missing then - the class defining the callback is assumed to be the - interceptor class or component class in scope at the - location in the descriptor in which the around invoke - definition appears. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="class" - type="javaee:fully-qualified-classType" - minOccurs="0"/> - <xsd:element name="method-name" - type="javaee:java-identifierType"/> - </xsd:sequence> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="assembly-descriptorType"> - <xsd:annotation> - <xsd:documentation> - - The assembly-descriptorType defines - application-assembly information. - - The application-assembly information consists of the - following parts: the definition of security roles, the - definition of method permissions, the definition of - transaction attributes for enterprise beans with - container-managed transaction demarcation, the definition - of interceptor bindings, a list of - methods to be excluded from being invoked, and a list of - exception types that should be treated as application exceptions. - - All the parts are optional in the sense that they are - omitted if the lists represented by them are empty. - - Providing an assembly-descriptor in the deployment - descriptor is optional for the ejb-jar file producer. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="security-role" - type="javaee:security-roleType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method-permission" - type="javaee:method-permissionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="container-transaction" - type="javaee:container-transactionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="interceptor-binding" - type="javaee:interceptor-bindingType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="message-destination" - type="javaee:message-destinationType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="exclude-list" - type="javaee:exclude-listType" - minOccurs="0"/> - <xsd:element name="application-exception" - type="javaee:application-exceptionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmp-fieldType"> - <xsd:annotation> - <xsd:documentation> - - The cmp-fieldType describes a container-managed field. The - cmp-fieldType contains an optional description of the field, - and the name of the field. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="field-name" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The field-name element specifies the name of a - container managed field. - - The name of the cmp-field of an entity bean with - cmp-version 2.x must begin with a lowercase - letter. This field is accessed by methods whose - names consists of the name of the field specified by - field-name in which the first letter is uppercased, - prefixed by "get" or "set". - - The name of the cmp-field of an entity bean with - cmp-version 1.x must denote a public field of the - enterprise bean class or one of its superclasses. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmp-versionType"> - <xsd:annotation> - <xsd:documentation> - - The cmp-versionType specifies the version of an entity bean - with container-managed persistence. It is used by - cmp-version elements. - - The value must be one of the two following: - - 1.x - 2.x - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="1.x"/> - <xsd:enumeration value="2.x"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmr-field-typeType"> - <xsd:annotation> - <xsd:documentation> - - The cmr-field-type element specifies the class of a - collection-valued logical relationship field in the entity - bean class. The value of an element using cmr-field-typeType - must be either: java.util.Collection or java.util.Set. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="java.util.Collection"/> - <xsd:enumeration value="java.util.Set"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="cmr-fieldType"> - <xsd:annotation> - <xsd:documentation> - - The cmr-fieldType describes the bean provider's view of - a relationship. It consists of an optional description, and - the name and the class type of a field in the source of a - role of a relationship. The cmr-field-name element - corresponds to the name used for the get and set accessor - methods for the relationship. The cmr-field-type element is - used only for collection-valued cmr-fields. It specifies the - type of the collection that is used. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="cmr-field-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The cmr-field-name element specifies the name of a - logical relationship field in the entity bean - class. The name of the cmr-field must begin with a - lowercase letter. This field is accessed by methods - whose names consist of the name of the field - specified by cmr-field-name in which the first - letter is uppercased, prefixed by "get" or "set". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmr-field-type" - type="javaee:cmr-field-typeType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="container-transactionType"> - <xsd:annotation> - <xsd:documentation> - - The container-transactionType specifies how the container - must manage transaction scopes for the enterprise bean's - method invocations. It defines an optional description, a - list of method elements, and a transaction attribute. The - transaction attribute is to be applied to all the specified - methods. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method" - type="javaee:methodType" - maxOccurs="unbounded"/> - <xsd:element name="trans-attribute" - type="javaee:trans-attributeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-classType contains the fully-qualified name of the - enterprise bean's class. It is used by ejb-class elements. - - Example: - - <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-jarType"> - <xsd:annotation> - <xsd:documentation> - - The ejb-jarType defines the root element of the EJB - deployment descriptor. It contains - - - an optional description of the ejb-jar file - - an optional display name - - an optional icon that contains a small and a large - icon file name - - structural information about all included - enterprise beans that is not specified through - annotations - - structural information about interceptor classes - - a descriptor for container managed relationships, - if any. - - an optional application-assembly descriptor - - an optional name of an ejb-client-jar file for the - ejb-jar. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="enterprise-beans" - type="javaee:enterprise-beansType" - minOccurs="0"/> - <xsd:element name="interceptors" - type="javaee:interceptorsType" - minOccurs="0"/> - <xsd:element name="relationships" - type="javaee:relationshipsType" - minOccurs="0"> - <xsd:unique name="relationship-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relation-name contains the name of a - relation. The name must be unique within - relationships. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:ejb-relation"/> - <xsd:field xpath="javaee:ejb-relation-name"/> - </xsd:unique> - </xsd:element> - <xsd:element name="assembly-descriptor" - type="javaee:assembly-descriptorType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Providing an assembly-descriptor in the deployment - descriptor is optional for the ejb-jar file - producer. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-client-jar" - type="javaee:pathType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The optional ejb-client-jar element specifies a JAR - file that contains the class files necessary for a - client program to access the - enterprise beans in the ejb-jar file. - - Example: - - <ejb-client-jar>employee_service_client.jar - </ejb-client-jar> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="version" - type="javaee:dewey-versionType" - fixed="3.0" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The version specifies the version of the - EJB specification that the instance document must - comply with. This information enables deployment tools - to validate a particular EJB Deployment - Descriptor with respect to a specific version of the EJB - schema. - - </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:complexType name="ejb-nameType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-nameType specifies an enterprise bean's name. It is - used by ejb-name elements. This name is assigned by the - ejb-jar file producer to name the enterprise bean in the - ejb-jar file's deployment descriptor. The name must be - unique among the names of the enterprise beans in the same - ejb-jar file. - - There is no architected relationship between the used - ejb-name in the deployment descriptor and the JNDI name that - the Deployer will assign to the enterprise bean's home. - - The name for an entity bean must conform to the lexical - rules for an NMTOKEN. - - Example: - - <ejb-name>EmployeeService</ejb-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:xsdNMTOKENType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-relationType"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationType describes a relationship between two - entity beans with container-managed persistence. It is used - by ejb-relation elements. It contains a description; an - optional ejb-relation-name element; and exactly two - relationship role declarations, defined by the - ejb-relationship-role elements. The name of the - relationship, if specified, is unique within the ejb-jar - file. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relation-name" - type="javaee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relation-name element provides a unique name - within the ejb-jar file for a relationship. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-relationship-role" - type="javaee:ejb-relationship-roleType"/> - <xsd:element name="ejb-relationship-role" - type="javaee:ejb-relationship-roleType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-relationship-roleType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The ejb-relationship-roleType describes a role within a - relationship. There are two roles in each relationship. - - The ejb-relationship-roleType contains an optional - description; an optional name for the relationship role; a - specification of the multiplicity of the role; an optional - specification of cascade-delete functionality for the role; - the role source; and a declaration of the cmr-field, if any, - by means of which the other side of the relationship is - accessed from the perspective of the role source. - - The multiplicity and role-source element are mandatory. - - The relationship-role-source element designates an entity - bean by means of an ejb-name element. For bidirectional - relationships, both roles of a relationship must declare a - relationship-role-source element that specifies a cmr-field - in terms of which the relationship is accessed. The lack of - a cmr-field element in an ejb-relationship-role specifies - that the relationship is unidirectional in navigability and - the entity bean that participates in the relationship is - "not aware" of the relationship. - - Example: - - <ejb-relation> - <ejb-relation-name>Product-LineItem</ejb-relation-name> - <ejb-relationship-role> - <ejb-relationship-role-name>product-has-lineitems - </ejb-relationship-role-name> - <multiplicity>One</multiplicity> - <relationship-role-source> - <ejb-name>ProductEJB</ejb-name> - </relationship-role-source> - </ejb-relationship-role> - </ejb-relation> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relationship-role-name" - type="javaee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationship-role-name element defines a - name for a role that is unique within an - ejb-relation. Different relationships can use the - same name for a role. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="multiplicity" - type="javaee:multiplicityType"/> - <xsd:element name="cascade-delete" - type="javaee:emptyType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The cascade-delete element specifies that, within a - particular relationship, the lifetime of one or more - entity beans is dependent upon the lifetime of - another entity bean. The cascade-delete element can - only be specified for an ejb-relationship-role - element contained in an ejb-relation element in - which the other ejb-relationship-role - element specifies a multiplicity of One. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="relationship-role-source" - type="javaee:relationship-role-sourceType"/> - <xsd:element name="cmr-field" - type="javaee:cmr-fieldType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="enterprise-beansType"> - <xsd:annotation> - <xsd:documentation> - - The enterprise-beansType declares one or more enterprise - beans. Each bean can be a session, entity or message-driven - bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:choice maxOccurs="unbounded"> - <xsd:element name="session" - type="javaee:session-beanType"> - <xsd:unique name="session-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be 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="session-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - 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="session-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-env-ref"/> - <xsd:field xpath="javaee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:message-destination-ref"/> - <xsd:field xpath="javaee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-ref"/> - <xsd:field xpath="javaee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="session-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:env-entry"/> - <xsd:field xpath="javaee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - <xsd:element name="entity" - type="javaee:entity-beanType"> - <xsd:unique name="entity-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be 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="entity-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - 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="entity-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-env-ref"/> - <xsd:field xpath="javaee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:message-destination-ref"/> - <xsd:field xpath="javaee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-ref"/> - <xsd:field xpath="javaee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="entity-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:env-entry"/> - <xsd:field xpath="javaee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - <xsd:element name="message-driven" - type="javaee:message-driven-beanType"> - <xsd:unique name="messaged-ejb-local-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 component's environment and is relative to the - java:comp/env context. The name must be unique within - the component. - - It is recommended that name be 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="messaged-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 - component's environment and is relative to the - java:comp/env context. The name must be unique - within the component. - - 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="messaged-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-env-ref"/> - <xsd:field xpath="javaee:resource-env-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 component - code. The name is a JNDI name relative to the - java:comp/env context and must be unique within an - component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:message-destination-ref"/> - <xsd:field xpath="javaee:message-destination-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-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 component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:resource-ref"/> - <xsd:field xpath="javaee:res-ref-name"/> - </xsd:unique> - - <xsd:unique name="messaged-env-entry-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The env-entry-name element contains the name of a - component's environment entry. The name is a JNDI - name relative to the java:comp/env context. The - name must be unique within an component. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:env-entry"/> - <xsd:field xpath="javaee:env-entry-name"/> - </xsd:unique> - </xsd:element> - - </xsd:choice> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="entity-beanType"> - <xsd:annotation> - <xsd:documentation> - - The entity-beanType declares an entity bean. The declaration - consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name - - a unique name assigned to the enterprise bean - in the deployment descriptor - - an optional mapped-name element that can be used to provide - vendor-specific deployment information such as the physical - jndi-name of the entity bean's remote home interface. This - element is not required to be supported by all implementations. - Any use of this element is non-portable. - - the names of the entity bean's remote home - and remote interfaces, if any - - the names of the entity bean's local home and local - interfaces, if any - - the entity bean's implementation class - - the optional entity bean's persistence management type. If - this element is not specified it is defaulted to Container. - - the entity bean's primary key class name - - an indication of the entity bean's reentrancy - - an optional specification of the - entity bean's cmp-version - - an optional specification of the entity bean's - abstract schema name - - an optional list of container-managed fields - - an optional specification of the primary key - field - - an optional declaration of the bean's environment - entries - - an optional declaration of the bean's EJB - references - - an optional declaration of the bean's local - EJB references - - an optional declaration of the bean's web - service references - - an optional declaration of the security role - references - - an optional declaration of the security identity - to be used for the execution of the bean's methods - - an optional declaration of the bean's - resource manager connection factory references - - an optional declaration of the bean's - resource environment references - - an optional declaration of the bean's message - destination references - - an optional set of query declarations - for finder and select methods for an entity - bean with cmp-version 2.x. - - The optional abstract-schema-name element must be specified - for an entity bean with container-managed persistence and - cmp-version 2.x. - - The optional primkey-field may be present in the descriptor - if the entity's persistence-type is Container. - - The optional cmp-version element may be present in the - descriptor if the entity's persistence-type is Container. If - the persistence-type is Container and the cmp-version - element is not specified, its value defaults to 2.x. - - The optional home and remote elements must be specified if - the entity bean cmp-version is 1.x. - - The optional home and remote elements must be specified if - the entity bean has a remote home and remote interface. - - The optional local-home and local elements must be specified - if the entity bean has a local home and local interface. - - Either both the local-home and the local elements or both - the home and the remote elements must be specified. - - The optional query elements must be present if the - persistence-type is Container and the cmp-version is 2.x and - query methods other than findByPrimaryKey have been defined - for the entity bean. - - The other elements that are optional are "optional" in the - sense that they are omitted if the lists represented by them - are empty. - - At least one cmp-field element must be present in the - descriptor if the entity's persistence-type is Container and - the cmp-version is 1.x, and none must not be present if the - entity's persistence-type is Bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="javaee:ejb-nameType"/> - <xsd:element name="mapped-name" - type="javaee:xsdStringType" - minOccurs="0"/> - <xsd:element name="home" - type="javaee:homeType" - minOccurs="0"/> - <xsd:element name="remote" - type="javaee:remoteType" - minOccurs="0"/> - <xsd:element name="local-home" - type="javaee:local-homeType" - minOccurs="0"/> - <xsd:element name="local" - type="javaee:localType" - minOccurs="0"/> - <xsd:element name="ejb-class" - type="javaee:ejb-classType"/> - <xsd:element name="persistence-type" - type="javaee:persistence-typeType"/> - <xsd:element name="prim-key-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The prim-key-class element contains the - fully-qualified name of an - entity bean's primary key class. - - If the definition of the primary key class is - deferred to deployment time, the prim-key-class - element should specify java.lang.Object. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="reentrant" - type="javaee:true-falseType"> - <xsd:annotation> - <xsd:documentation> - - The reentrant element specifies whether an entity - bean is reentrant or not. - - The reentrant element must be one of the two - following: true or false - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmp-version" - type="javaee:cmp-versionType" - minOccurs="0"/> - <xsd:element name="abstract-schema-name" - type="javaee:java-identifierType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The abstract-schema-name element specifies the name - of the abstract schema type of an entity bean with - cmp-version 2.x. It is used in EJB QL queries. - - For example, the abstract-schema-name for an entity - bean whose local interface is - com.acme.commerce.Order might be Order. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="cmp-field" - type="javaee:cmp-fieldType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="primkey-field" - type="javaee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The primkey-field element is used to specify the - name of the primary key field for an entity with - container-managed persistence. - - The primkey-field must be one of the fields declared - in the cmp-field element, and the type of the field - must be the same as the primary key type. - - The primkey-field element is not used if the primary - key maps to multiple container-managed fields - (i.e. the key is a compound key). In this case, the - fields of the primary key class must be public, and - their names must correspond to the field names of - the entity bean class that comprise the key. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> - <xsd:element name="security-role-ref" - type="javaee:security-role-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="security-identity" - type="javaee:security-identityType" - minOccurs="0"/> - <xsd:element name="query" - type="javaee:queryType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="exclude-listType"> - <xsd:annotation> - <xsd:documentation> - - The exclude-listType specifies one or more methods which - the Assembler marks to be uncallable. - - If the method permission relation contains methods that are - in the exclude list, the Deployer should consider those - methods to be uncallable. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="method" - type="javaee:methodType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="init-methodType"> - <xsd:sequence> - <xsd:element name="create-method" - type="javaee:named-methodType"/> - <xsd:element name="bean-method" - type="javaee:named-methodType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="interceptor-bindingType"> - <xsd:annotation> - <xsd:documentation> - - The interceptor-bindingType element describes the binding of - interceptor classes to beans within the ejb-jar. - It consists of : - - - An optional description. - - The name of an ejb within the ejb-jar or the wildcard value "*", - which is used to define interceptors that are bound to all - beans in the ejb-jar. - - A list of interceptor classes that are bound to the contents of - the ejb-name element or a specification of the total ordering - over the interceptors defined for the given level and above. - - An optional exclude-default-interceptors element. If set to true, - specifies that default interceptors are not to be applied to - a bean-class and/or business method. - - An optional exclude-class-interceptors element. If set to true, - specifies that class interceptors are not to be applied to - a business method. - - An optional set of method elements for describing the name/params - of a method-level interceptor. - - Interceptors bound to all classes using the wildcard syntax - "*" are default interceptors for the components in the ejb-jar. - In addition, interceptors may be bound at the level of the bean - class (class-level interceptors) or business methods (method-level - interceptors ). - - The binding of interceptors to classes is additive. If interceptors - are bound at the class-level and/or default-level as well as the - method-level, both class-level and/or default-level as well as - method-level will apply. - - There are four possible styles of the interceptor element syntax : - - 1. - <interceptor-binding> - <ejb-name>*</ejb-name> - <interceptor-class>INTERCEPTOR</interceptor-class> - </interceptor-binding> - - Specifying the ejb-name as the wildcard value "*" designates - default interceptors (interceptors that apply to all session and - message-driven beans contained in the ejb-jar). - - 2. - <interceptor-binding> - <ejb-name>EJBNAME</ejb-name> - <interceptor-class>INTERCEPTOR</interceptor-class> - </interceptor-binding> - - This style is used to refer to interceptors associated with the - specified enterprise bean(class-level interceptors). - - 3. - <interceptor-binding> - <ejb-name>EJBNAME</ejb-name> - <interceptor-class>INTERCEPTOR</interceptor-class> - <method> - <method-name>METHOD</method-name> - </method> - </interceptor-binding> - - This style is used to associate a method-level interceptor with - the specified enterprise bean. If there are multiple methods - with the same overloaded name, the element of this style refers - to all the methods with the overloaded name. Method-level - interceptors can only be associated with business methods of the - bean class. Note that the wildcard value "*" cannot be used - to specify method-level interceptors. - - 4. - <interceptor-binding> - <ejb-name>EJBNAME</ejb-name> - <interceptor-class>INTERCEPTOR</interceptor-class> - <method> - <method-name>METHOD</method-name> - <method-params> - <method-param>PARAM-1</method-param> - <method-param>PARAM-2</method-param> - ... - <method-param>PARAM-N</method-param> - </method-params> - </method> - </interceptor-binding> - - This style is used to associate a method-level interceptor with - the specified method of the specified enterprise bean. This - style is used to refer to a single method within a set of methods - with an overloaded name. The values PARAM-1 through PARAM-N - are the fully-qualified Java types of the method's input parameters - (if the method has no input arguments, the method-params element - contains no method-param elements). Arrays are specified by the - array element's type, followed by one or more pair of square - brackets (e.g. int[][]). - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-name" - type="javaee:string"/> - <xsd:choice> - <xsd:element name="interceptor-class" - type="javaee:fully-qualified-classType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="interceptor-order" - type="javaee:interceptor-orderType" - minOccurs="1"/> - </xsd:choice> - <xsd:element name="exclude-default-interceptors" - type="javaee:true-falseType" - minOccurs="0"/> - <xsd:element name="exclude-class-interceptors" - type="javaee:true-falseType" - minOccurs="0"/> - <xsd:element name="method" - type="javaee:named-methodType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="interceptor-orderType"> - <xsd:annotation> - <xsd:documentation> - The interceptor-orderType element describes a total ordering - of interceptor classes. - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - - <xsd:element name="interceptor-class" - type="javaee:fully-qualified-classType" - minOccurs="1" - maxOccurs="unbounded"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="interceptorType"> - <xsd:annotation> - <xsd:documentation> - - The interceptorType element declares information about a single - interceptor class. It consists of : - - - An optional description. - - The fully-qualified name of the interceptor class. - - An optional list of around invoke methods declared on the - interceptor class and/or its super-classes. - - An optional list environment dependencies for the interceptor - class and/or its super-classes. - - An optional list of post-activate methods declared on the - interceptor class and/or its super-classes. - - An optional list of pre-passivate methods declared on the - interceptor class and/or its super-classes. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="interceptor-class" - type="javaee:fully-qualified-classType"/> - <xsd:element name="around-invoke" - type="javaee:around-invokeType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> - <xsd:element name="post-activate" - type="javaee:lifecycle-callbackType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="pre-passivate" - type="javaee:lifecycle-callbackType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="interceptorsType"> - <xsd:annotation> - <xsd:documentation> - - The interceptorsType element declares one or more interceptor - classes used by components within this ejb-jar. The declaration - consists of : - - - An optional description. - - One or more interceptor elements. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="interceptor" - type="javaee:interceptorType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-driven-beanType"> - <xsd:annotation> - <xsd:documentation> - - The message-driven element declares a message-driven - bean. The declaration consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name. - - a name assigned to the enterprise bean in - the deployment descriptor - - an optional mapped-name element that can be used to provide - vendor-specific deployment information such as the physical - jndi-name of destination from which this message-driven bean - should consume. This element is not required to be supported - by all implementations. Any use of this element is non-portable. - - the message-driven bean's implementation class - - an optional declaration of the bean's messaging - type - - an optional declaration of the bean's timeout method. - - the optional message-driven bean's transaction management - type. If it is not defined, it is defaulted to Container. - - an optional declaration of the bean's - message-destination-type - - an optional declaration of the bean's - message-destination-link - - an optional declaration of the message-driven bean's - activation configuration properties - - an optional list of the message-driven bean class and/or - superclass around-invoke methods. - - an optional declaration of the bean's environment - entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local EJB - references - - an optional declaration of the bean's web service - references - - an optional declaration of the security - identity to be used for the execution of the bean's - methods - - an optional declaration of the bean's - resource manager connection factory - references - - an optional declaration of the bean's resource - environment references. - - an optional declaration of the bean's message - destination references - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="javaee:ejb-nameType"/> - <xsd:element name="mapped-name" - type="javaee:xsdStringType" - minOccurs="0"/> - <xsd:element name="ejb-class" - type="javaee:ejb-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-class element specifies the fully qualified name - of the bean class for this ejb. It is required unless - there is a component-defining annotation for the same - ejb-name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="messaging-type" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The messaging-type element specifies the message - listener interface of the message-driven bean. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="timeout-method" - type="javaee:named-methodType" - minOccurs="0"/> - <xsd:element name="transaction-type" - type="javaee:transaction-typeType" - minOccurs="0"/> - <xsd:element name="message-destination-type" - type="javaee:message-destination-typeType" - minOccurs="0"/> - <xsd:element name="message-destination-link" - type="javaee:message-destination-linkType" - minOccurs="0"/> - <xsd:element name="activation-config" - type="javaee:activation-configType" - minOccurs="0"/> - <xsd:element name="around-invoke" - type="javaee:around-invokeType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> - <xsd:element name="security-identity" - type="javaee:security-identityType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-intfType"> - - <xsd:annotation> - <xsd:documentation> - - The method-intf element allows a method element to - differentiate between the methods with the same name and - signature that are multiply defined across the home and - component interfaces (e.g, in both an enterprise bean's - remote and local interfaces or in both an enterprise bean's - home and remote interfaces, etc.); the component and web - service endpoint interfaces, and so on. The Local applies to - both local component interface and local business interface. - Similarly, Remote applies to both remote component interface - and the remote business interface. - - The method-intf element must be one of the following: - - Home - Remote - LocalHome - Local - ServiceEndpoint - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="Home"/> - <xsd:enumeration value="Remote"/> - <xsd:enumeration value="LocalHome"/> - <xsd:enumeration value="Local"/> - <xsd:enumeration value="ServiceEndpoint"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-nameType"> - <xsd:annotation> - <xsd:documentation> - - The method-nameType contains a name of an enterprise - bean method or the asterisk (*) character. The asterisk is - used when the element denotes all the methods of an - enterprise bean's client view interfaces. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-paramsType"> - <xsd:annotation> - <xsd:documentation> - - The method-paramsType defines a list of the - fully-qualified Java type names of the method parameters. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="method-param" - type="javaee:java-typeType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The method-param element contains a primitive - or a fully-qualified Java type name of a method - parameter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-permissionType"> - <xsd:annotation> - <xsd:documentation> - - The method-permissionType specifies that one or more - security roles are allowed to invoke one or more enterprise - bean methods. The method-permissionType consists of an - optional description, a list of security role names or an - indicator to state that the method is unchecked for - authorization, and a list of method elements. - - The security roles used in the method-permissionType - must be defined in the security-role elements of the - deployment descriptor, and the methods must be methods - defined in the enterprise bean's business, home, component - and/or web service endpoint interfaces. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="role-name" - type="javaee:role-nameType" - maxOccurs="unbounded"/> - <xsd:element name="unchecked" - type="javaee:emptyType"> - <xsd:annotation> - <xsd:documentation> - - The unchecked element specifies that a method is - not checked for authorization by the container - prior to invocation of the method. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - <xsd:element name="method" - type="javaee:methodType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="methodType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The methodType is used to denote a method of an enterprise - bean's business, home, component, and/or web service endpoint - interface, or, in the case of a message-driven bean, the - bean's message listener method, or a set of such - methods. The ejb-name element must be the name of one of the - enterprise beans declared in the deployment descriptor; the - optional method-intf element allows to distinguish between a - method with the same signature that is multiply defined - across the business, home, component, and/or web service - endpoint nterfaces; the method-name element specifies the - method name; and the optional method-params elements identify - a single method among multiple methods with an overloaded - method name. - - There are three possible styles of using methodType element - within a method element: - - 1. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>*</method-name> - </method> - - This style is used to refer to all the methods of the - specified enterprise bean's business, home, component, - and/or web service endpoint interfaces. - - 2. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - </method> - - This style is used to refer to the specified method of - the specified enterprise bean. If there are multiple - methods with the same overloaded name, the element of - this style refers to all the methods with the overloaded - name. - - 3. - <method> - <ejb-name>EJBNAME</ejb-name> - <method-name>METHOD</method-name> - <method-params> - <method-param>PARAM-1</method-param> - <method-param>PARAM-2</method-param> - ... - <method-param>PARAM-n</method-param> - </method-params> - </method> - - This style is used to refer to a single method within a - set of methods with an overloaded name. PARAM-1 through - PARAM-n are the fully-qualified Java types of the - method's input parameters (if the method has no input - arguments, the method-params element contains no - method-param elements). Arrays are specified by the - array element's type, followed by one or more pair of - square brackets (e.g. int[][]). If there are multiple - methods with the same overloaded name, this style refers - to all of the overloaded methods. - - Examples: - - Style 1: The following method element refers to all the - methods of the EmployeeService bean's business, home, - component, and/or web service endpoint interfaces: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>*</method-name> - </method> - - Style 2: The following method element refers to all the - create methods of the EmployeeService bean's home - interface(s). - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - </method> - - Style 3: The following method element refers to the - create(String firstName, String LastName) method of the - EmployeeService bean's home interface(s). - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - The following example illustrates a Style 3 element with - more complex parameter types. The method - foobar(char s, int i, int[] iar, mypackage.MyClass mycl, - mypackage.MyClass[][] myclaar) would be specified as: - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-name>foobar</method-name> - <method-params> - <method-param>char</method-param> - <method-param>int</method-param> - <method-param>int[]</method-param> - <method-param>mypackage.MyClass</method-param> - <method-param>mypackage.MyClass[][]</method-param> - </method-params> - </method> - - The optional method-intf element can be used when it becomes - necessary to differentiate between a method that is multiply - defined across the enterprise bean's business, home, component, - and/or web service endpoint interfaces with the same name and - signature. However, if the same method is a method of both the - local business interface, and the local component interface, - the same attribute applies to the method for both interfaces. - Likewise, if the same method is a method of both the remote - business interface and the remote component interface, the same - attribute applies to the method for both interfaces. - - For example, the method element - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Remote</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - can be used to differentiate the create(String, String) - method defined in the remote interface from the - create(String, String) method defined in the remote home - interface, which would be defined as - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - and the create method that is defined in the local home - interface which would be defined as - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>LocalHome</method-intf> - <method-name>create</method-name> - <method-params> - <method-param>java.lang.String</method-param> - <method-param>java.lang.String</method-param> - </method-params> - </method> - - The method-intf element can be used with all three Styles - of the method element usage. For example, the following - method element example could be used to refer to all the - methods of the EmployeeService bean's remote home interface - and the remote business interface. - - <method> - <ejb-name>EmployeeService</ejb-name> - <method-intf>Home</method-intf> - <method-name>*</method-name> - </method> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-name" - type="javaee:ejb-nameType"/> - <xsd:element name="method-intf" - type="javaee:method-intfType" - minOccurs="0"> - </xsd:element> - <xsd:element name="method-name" - type="javaee:method-nameType"/> - <xsd:element name="method-params" - type="javaee:method-paramsType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="multiplicityType"> - <xsd:annotation> - <xsd:documentation> - - The multiplicityType describes the multiplicity of the - role that participates in a relation. - - The value must be one of the two following: - - One - Many - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="One"/> - <xsd:enumeration value="Many"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="named-methodType"> - <xsd:sequence> - <xsd:element name="method-name" - type="javaee:string"/> - <xsd:element name="method-params" - type="javaee:method-paramsType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="persistence-typeType"> - <xsd:annotation> - <xsd:documentation> - - The persistence-typeType specifies an entity bean's persistence - management type. - - The persistence-type element must be one of the two following: - - Bean - Container - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="Bean"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="query-methodType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The query-method specifies the method for a finder or select - query. - - The method-name element specifies the name of a finder or select - method in the entity bean's implementation class. - - Each method-param must be defined for a query-method using the - method-params element. - - It is used by the query-method element. - - Example: - - <query> - <description>Method finds large orders</description> - <query-method> - <method-name>findLargeOrders</method-name> - <method-params></method-params> - </query-method> - <ejb-ql> - SELECT OBJECT(o) FROM Order o - WHERE o.amount > 1000 - </ejb-ql> - </query> - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="method-name" - type="javaee:method-nameType"/> - <xsd:element name="method-params" - type="javaee:method-paramsType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="queryType"> - <xsd:annotation> - <xsd:documentation> - - The queryType defines a finder or select - query. It contains - - an optional description of the query - - the specification of the finder or select - method it is used by - - an optional specification of the result type - mapping, if the query is for a select method - and entity objects are returned. - - the EJB QL query string that defines the query. - - Queries that are expressible in EJB QL must use the ejb-ql - element to specify the query. If a query is not expressible - in EJB QL, the description element should be used to - describe the semantics of the query and the ejb-ql element - should be empty. - - The result-type-mapping is an optional element. It can only - be present if the query-method specifies a select method - that returns entity objects. The default value for the - result-type-mapping element is "Local". - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" minOccurs="0"/> - <xsd:element name="query-method" - type="javaee:query-methodType"/> - <xsd:element name="result-type-mapping" - type="javaee:result-type-mappingType" - minOccurs="0"/> - <xsd:element name="ejb-ql" - type="javaee:xsdStringType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="relationship-role-sourceType"> - <xsd:annotation> - <xsd:documentation> - - The relationship-role-sourceType designates the source of a - role that participates in a relationship. A - relationship-role-sourceType is used by - relationship-role-source elements to uniquely identify an - entity bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-name" - type="javaee:ejb-nameType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="relationshipsType"> - <xsd:annotation> - <xsd:documentation> - - The relationshipsType describes the relationships in - which entity beans with container-managed persistence - participate. The relationshipsType contains an optional - description; and a list of ejb-relation elements, which - specify the container managed relationships. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-relation" - type="javaee:ejb-relationType" - maxOccurs="unbounded"> - - <xsd:unique name="role-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The ejb-relationship-role-name contains the name of a - relationship role. The name must be unique within - a relationship, but can be reused in different - relationships. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector - xpath=".//javaee:ejb-relationship-role-name"/> - <xsd:field - xpath="."/> - </xsd:unique> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="remove-methodType"> - <xsd:sequence> - <xsd:element name="bean-method" - type="javaee:named-methodType"/> - <xsd:element name="retain-if-exception" - type="javaee:true-falseType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="result-type-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The result-type-mappingType is used in the query element to - specify whether an abstract schema type returned by a query - for a select method is to be mapped to an EJBLocalObject or - EJBObject type. - - The value must be one of the following: - - Local - Remote - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="Local"/> - <xsd:enumeration value="Remote"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-identityType"> - <xsd:annotation> - <xsd:documentation> - - The security-identityType specifies whether the caller's - security identity is to be used for the execution of the - methods of the enterprise bean or whether a specific run-as - identity is to be used. It contains an optional description - and a specification of the security identity to be used. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="use-caller-identity" - type="javaee:emptyType"> - <xsd:annotation> - <xsd:documentation> - - The use-caller-identity element specifies that - the caller's security identity be used as the - security identity for the execution of the - enterprise bean's methods. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="run-as" - type="javaee:run-asType"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-beanType"> - <xsd:annotation> - <xsd:documentation> - - The session-beanType declares an session bean. The - declaration consists of: - - - an optional description - - an optional display name - - an optional icon element that contains a small and a large - icon file name - - a name assigned to the enterprise bean - in the deployment description - - an optional mapped-name element that can be used to provide - vendor-specific deployment information such as the physical - jndi-name of the session bean's remote home/business interface. - This element is not required to be supported by all - implementations. Any use of this element is non-portable. - - the names of all the remote or local business interfaces, - if any - - the names of the session bean's remote home and - remote interfaces, if any - - the names of the session bean's local home and - local interfaces, if any - - the name of the session bean's web service endpoint - interface, if any - - the session bean's implementation class - - the session bean's state management type - - an optional declaration of the session bean's timeout method. - - the optional session bean's transaction management type. - If it is not present, it is defaulted to Container. - - an optional list of the session bean class and/or - superclass around-invoke methods. - - an optional declaration of the bean's - environment entries - - an optional declaration of the bean's EJB references - - an optional declaration of the bean's local - EJB references - - an optional declaration of the bean's web - service references - - an optional declaration of the security role - references - - an optional declaration of the security identity - to be used for the execution of the bean's methods - - an optional declaration of the bean's resource - manager connection factory references - - an optional declaration of the bean's resource - environment references. - - an optional declaration of the bean's message - destination references - - The elements that are optional are "optional" in the sense - that they are omitted when if lists represented by them are - empty. - - Either both the local-home and the local elements or both - the home and the remote elements must be specified for the - session bean. - - The service-endpoint element may only be specified if the - bean is a stateless session bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="ejb-name" - type="javaee:ejb-nameType"/> - <xsd:element name="mapped-name" - type="javaee:xsdStringType" - minOccurs="0"/> - <xsd:element name="home" - type="javaee:homeType" - minOccurs="0"/> - <xsd:element name="remote" - type="javaee:remoteType" - minOccurs="0"/> - <xsd:element name="local-home" - type="javaee:local-homeType" - minOccurs="0"/> - <xsd:element name="local" - type="javaee:localType" - minOccurs="0"/> - <xsd:element name="business-local" - type="javaee:fully-qualified-classType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="business-remote" - type="javaee:fully-qualified-classType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="service-endpoint" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The service-endpoint element contains the - fully-qualified name of the enterprise bean's web - service endpoint interface. The service-endpoint - element may only be specified for a stateless - session bean. The specified interface must be a - valid JAX-RPC service endpoint interface. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="ejb-class" - type="javaee:ejb-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The ejb-class element specifies the fully qualified name - of the bean class for this ejb. It is required unless - there is a component-defining annotation for the same - ejb-name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="session-type" - type="javaee:session-typeType" - minOccurs="0"/> - <xsd:element name="timeout-method" - type="javaee:named-methodType" - minOccurs="0"/> - <xsd:element name="init-method" - type="javaee:init-methodType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The init-method element specifies the mappings for - EJB 2.x style create methods for an EJB 3.0 bean. - This element can only be specified for stateful - session beans. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="remove-method" - type="javaee:remove-methodType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The remove-method element specifies the mappings for - EJB 2.x style remove methods for an EJB 3.0 bean. - This element can only be specified for stateful - session beans. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="transaction-type" - type="javaee:transaction-typeType" - minOccurs="0"/> - <xsd:element name="around-invoke" - type="javaee:around-invokeType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> - <xsd:element name="post-activate" - type="javaee:lifecycle-callbackType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="pre-passivate" - type="javaee:lifecycle-callbackType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="security-role-ref" - type="javaee:security-role-refType" - minOccurs="0" - maxOccurs="unbounded"> - </xsd:element> - <xsd:element name="security-identity" - type="javaee:security-identityType" - minOccurs="0"> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-typeType"> - <xsd:annotation> - <xsd:documentation> - - The session-typeType describes whether the session bean is a - stateful session or stateless session. It is used by - session-type elements. - - The value must be one of the two following: - - Stateful - Stateless - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="Stateful"/> - <xsd:enumeration value="Stateless"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="trans-attributeType"> - <xsd:annotation> - <xsd:documentation> - - The trans-attributeType specifies how the container must - manage the transaction boundaries when delegating a method - invocation to an enterprise bean's business method. - - The value must be one of the following: - - NotSupported - Supports - Required - RequiresNew - Mandatory - Never - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="NotSupported"/> - <xsd:enumeration value="Supports"/> - <xsd:enumeration value="Required"/> - <xsd:enumeration value="RequiresNew"/> - <xsd:enumeration value="Mandatory"/> - <xsd:enumeration value="Never"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="transaction-typeType"> - <xsd:annotation> - <xsd:documentation> - - The transaction-typeType specifies an enterprise bean's - transaction management type. - - The transaction-type must be one of the two following: - - Bean - Container - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="Bean"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_1_4.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_1_4.xsd deleted file mode 100644 index 9b2334c2e3..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_1_4.xsd +++ /dev/null @@ -1,1608 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xsd:schema - targetNamespace="http://java.sun.com/xml/ns/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.4"> - <xsd:annotation> - <xsd:documentation> - @(#)j2ee_1_4.xsds 1.43 03/09/16 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </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:import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2001/xml.xsd"/> - - <xsd:include schemaLocation= - "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/> - - -<!-- **************************************************** --> - - <xsd:group name="descriptionGroup"> - <xsd:annotation> - <xsd:documentation> - - This group keeps the usage of the contained description related - elements consistent across J2EE deployment descriptors. - - All elements may occur multiple times with different languages, - to support localization of the content. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="display-name" - type="j2ee:display-nameType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="icon" - type="j2ee:iconType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="descriptionType"> - <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 base="j2ee:xsdStringType"> - <xsd:attribute ref="xml:lang"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="dewey-versionType"> - <xsd:annotation> - <xsd:documentation> - - This type defines a dewey decimal which is used - to describe versions of documents. - - </xsd:documentation> - </xsd:annotation> - - <xsd:restriction base="xsd:decimal"> - <xsd:whiteSpace value="collapse"/> - </xsd:restriction> - - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:complexType name="display-nameType"> - <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 base="j2ee:string"> - <xsd:attribute ref="xml:lang"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-linkType"> - <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 J2EE 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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-local-refType"> - <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. 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 expected type of the referenced enterprise bean - - the expected local home and local interfaces of the - referenced enterprise bean - - optional ejb-link information, used to specify the - referenced enterprise bean - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-ref-name" - type="j2ee:ejb-ref-nameType"/> - <xsd:element name="ejb-ref-type" - type="j2ee:ejb-ref-typeType"/> - <xsd:element name="local-home" - type="j2ee:local-homeType"/> - <xsd:element name="local" - type="j2ee:localType"/> - <xsd:element name="ejb-link" - type="j2ee:ejb-linkType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-ref-nameType"> - <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:restriction base="j2ee:jndi-nameType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-ref-typeType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="Entity"/> - <xsd:enumeration value="Session"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-refType"> - <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. 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 expected type of the referenced enterprise bean - - the expected home and remote interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the - referenced enterprise bean - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-ref-name" - type="j2ee:ejb-ref-nameType"/> - <xsd:element name="ejb-ref-type" - type="j2ee:ejb-ref-typeType"/> - - <xsd:element name="home" - type="j2ee:homeType"/> - <xsd:element name="remote" - type="j2ee:remoteType"/> - <xsd:element name="ejb-link" - type="j2ee:ejb-linkType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="emptyType"> - <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:complexType name="env-entry-type-valuesType"> - <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:restriction base="j2ee:string"> - <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:complexType name="env-entryType"> - <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, and an - optional value. If a value is not specified, one must be - supplied during deployment. - - It is used by env-entry elements. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="env-entry-name" - type="j2ee:jndi-nameType"> - <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:element name="env-entry-type" - type="j2ee:env-entry-type-valuesType"/> - - <xsd:element name="env-entry-value" - type="j2ee:xsdStringType" - minOccurs="0"> - <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:complexType name="fully-qualified-classType"> - <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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="generic-booleanType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="true"/> - <xsd:enumeration value="false"/> - <xsd:enumeration value="yes"/> - <xsd:enumeration value="no"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="homeType"> - <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:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="iconType"> - <xsd:annotation> - <xsd:documentation> - - The icon type contains small-icon and large-icon elements - that specify the file names for small and large GIF or - JPEG 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:element name="small-icon" type="j2ee:pathType" - minOccurs="0"> - <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 either in the JPEG or GIF format. - The icon can be used by tools. - - Example: - - <small-icon>employee-service-icon16x16.jpg</small-icon> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="large-icon" type="j2ee:pathType" - minOccurs="0"> - <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 either in the JPEG or GIF 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 ref="xml:lang"/> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-identifierType"> - <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:restriction base="j2ee:string"> - <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-typeType"> - <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:restriction base="j2ee:string"> - <xsd:pattern value="[^\p{Z}]*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jndi-nameType"> - <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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:group name="jndiEnvironmentRefsGroup"> - <xsd:annotation> - <xsd:documentation> - - This group keeps the usage of the contained JNDI environment - reference elements consistent across J2EE deployment descriptors. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="env-entry" - type="j2ee:env-entryType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-ref" - type="j2ee:ejb-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="ejb-local-ref" - type="j2ee:ejb-local-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:group ref="j2ee:service-refGroup"/> - <xsd:element name="resource-ref" - type="j2ee:resource-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="resource-env-ref" - type="j2ee:resource-env-refType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="message-destination-ref" - type="j2ee:message-destination-refType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="listenerType"> - <xsd:annotation> - <xsd:documentation> - - The listenerType indicates the deployment properties for a web - application listener bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="listener-class" - type="j2ee:fully-qualified-classType"> - <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:complexType name="local-homeType"> - <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:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="localType"> - <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:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-linkType"> - <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 J2EE 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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-refType"> - <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 - - the message destination type - - a specification as to whether the - destination is used for - consuming or producing messages, or both - - a link to the message destination - - 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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="message-destination-ref-name" - type="j2ee:jndi-nameType"> - <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:element name="message-destination-type" - type="j2ee:message-destination-typeType"/> - <xsd:element name="message-destination-usage" - type="j2ee:message-destination-usageType"/> - <xsd:element name="message-destination-link" - type="j2ee:message-destination-linkType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-typeType"> - <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:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-usageType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="Consumes"/> - <xsd:enumeration value="Produces"/> - <xsd:enumeration value="ConsumesProduces"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destinationType"> - <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. - - Example: - - <message-destination> - <message-destination-name>CorporateStocks - </message-destination-name> - </message-destination> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="message-destination-name" - type="j2ee:string"> - <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:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="param-valueType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="param-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The param-name element contains the name of a - parameter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="param-value" - type="j2ee:xsdStringType"> - <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:complexType name="pathType"> - <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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="remoteType"> - <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:restriction base="j2ee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="res-authType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="Application"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="res-sharing-scopeType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="Shareable"/> - <xsd:enumeration value="Unshareable"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="resource-env-refType"> - <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 indication of - the resource environment reference type expected by the - Deployment Component code. - - 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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="resource-env-ref-name" - type="j2ee:jndi-nameType"> - <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:element name="resource-env-ref-type" - type="j2ee:fully-qualified-classType"> - <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:complexType name="resource-refType"> - <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, the indication of the - resource manager connection factory type expected by the - Deployment Component code, the type of authentication - (Application or Container), and an optional specification of - the shareability of connections obtained from the resource - (Shareable or Unshareable). - - 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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="res-ref-name" - type="j2ee:jndi-nameType"> - <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:element name="res-type" - type="j2ee:fully-qualified-classType"> - <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:element name="res-auth" - type="j2ee:res-authType"/> - - <xsd:element name="res-sharing-scope" - type="j2ee:res-sharing-scopeType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="role-nameType"> - <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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="run-asType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="j2ee:role-nameType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-role-refType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="j2ee:role-nameType"> - <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:element name="role-link" - type="j2ee:role-nameType" - minOccurs="0"> - <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:complexType name="security-roleType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="j2ee:role-nameType"/> - </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 J2EE 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:complexType name="true-falseType"> - <xsd:annotation> - <xsd:documentation> - - This simple type designates a boolean with only two - permissible values - - - true - - false - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:xsdBooleanType"> - <xsd:pattern value="(true|false)"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="url-patternType"> - <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:complexType name="xsdAnyURIType"> - <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:complexType name="xsdBooleanType"> - <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:complexType name="xsdIntegerType"> - <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:complexType name="xsdNMTOKENType"> - <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:complexType name="xsdNonNegativeIntegerType"> - <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:complexType name="xsdPositiveIntegerType"> - <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:complexType name="xsdQNameType"> - <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:complexType name="xsdStringType"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_jaxrpc_mapping_1_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_jaxrpc_mapping_1_1.xsd deleted file mode 100644 index 852191c298..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_jaxrpc_mapping_1_1.xsd +++ /dev/null @@ -1,886 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.1"> - <xsd:annotation> - <xsd:documentation> - @(#)j2ee_jaxrpc_mapping_1_1.xsds 1.11 09/03/03 - - Based on j2ee_jaxrpc_mapping_1_0.dtd, Last updated: 09/19/2002 10:26 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - (C) Copyright International Business Machines Corporation 2002 - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The element describes the Java mapping to a known WSDL document. - - It contains the mapping between package names and XML namespaces, - WSDL root types and Java artifacts, and the set of mappings for - services. - - All java-wsdl-mapping deployment descriptors must indicate the - schema by using the J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and by indicating the version of the schema by using the - version element as shown below: - - <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd" - version="1.1"> - ... - </java-wsdl-mapping> - - The instance documents may indicate the published version of - the schema using the xsi:schemaLocation attribute for J2EE - namespace with the following location: - - http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="java-wsdl-mapping" type="j2ee:java-wsdl-mappingType"> - <xsd:annotation> - <xsd:documentation> - - This is the root of the java-wsdl-mapping deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="constructor-parameter-orderType"> - <xsd:annotation> - <xsd:documentation> - - The constructor-parameter-order element defines the order - that complexType element values are applied to a Java - exception constructor. Element names are specified for each - parameter of the constructor, including element names of - inherited types if necessary. - - Used in: exception-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="element-name" - type="j2ee:string" - minOccurs="1" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The element-name element defines the name of a complexType - element name attribute value. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="exception-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The exception-mapping element defines the mapping between the - service specific exception types and wsdl faults and - SOAP headerfaults. - - This element should be interpreted with respect to the - mapping between a method and an operation which provides the - mapping context. - - Used in: service-endpoint-method-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="exception-type" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The exception-type element defines Java type of the exception. - It may be a service specific exception. - - It must be a fully qualified class name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-message" - type="j2ee:wsdl-messageType"/> - <xsd:element name="wsdl-message-part-name" - type="j2ee:wsdl-message-part-nameType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-message-part-name element is required only - when the message referenced by the wsdl-message element - has more than one part. - - This only occurs when multiple headerfaults use the - same message. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="constructor-parameter-order" - type="j2ee:constructor-parameter-orderType" - minOccurs="0" maxOccurs="1"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-wsdl-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The element describes the Java mapping to a known WSDL document. - - It contains the mapping between package names and XML namespaces, - WSDL root types and Java artifacts, and the set of mappings for - services. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="package-mapping" - type="j2ee:package-mappingType" - minOccurs="1" maxOccurs="unbounded"/> - <xsd:element name="java-xml-type-mapping" - type="j2ee:java-xml-type-mappingType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="exception-mapping" - type="j2ee:exception-mappingType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:sequence minOccurs="0" maxOccurs="unbounded"> - <xsd:element name="service-interface-mapping" - type="j2ee:service-interface-mappingType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="service-endpoint-interface-mapping" - type="j2ee:service-endpoint-interface-mappingType" - minOccurs="1" maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:sequence> - - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="1.1" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 1.1. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-xml-type-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The java-xml-type-mapping element contains a java-type that is the - fully qualified name of the Java class, primitive type, or array - type, QName of the XML root type or anonymous type, the WSDL type - scope the QName applies to and the set of variable mappings for - each public variable within the Java class. - - Used in: java-wsdl-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="java-type" - type="j2ee:java-typeType"> - <xsd:annotation> - <xsd:documentation> - - The java-type element is the fully qualified class name of - a Java class, primitive, or array type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <choice> - <xsd:element name="root-type-qname" - type="j2ee:xsdQNameType"> - <xsd:annotation> - <xsd:documentation> - - The root-type-qname identifies the WSDL QName of an XML type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="anonymous-type-qname" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The anonymous-type-qname identifies the WSDL QName of an - anonymous XML type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </choice> - <xsd:element name="qname-scope" - type="j2ee:qname-scopeType"/> - <xsd:element name="variable-mapping" - type="j2ee:variable-mappingType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="method-param-parts-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The method-param-parts-mapping element defines the mapping between a - Java method parameters and a wsdl-message. - - Used in: service-endpoint-method-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="param-position" - type="j2ee:xsdNonNegativeIntegerType"> - <xsd:annotation> - <xsd:documentation> - - The param-position element defines the position of a - parameter within a Java method. It must be an integer - starting from 0. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="param-type" - type="j2ee:java-typeType"> - <xsd:annotation> - <xsd:documentation> - - The param-type element defines the fully qualified - class name of a Java class, primitive, or array type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-message-mapping" - type="j2ee:wsdl-message-mappingType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="package-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The package-mapping indicates the mapping between java-package-name - and XML namespace in the WSDL document. - - Used in: java-wsdl-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="package-type" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The package-type indicates the Java package name. It must be a fully - qualified package name, even though the XML schema type is - fully-qualified-classType. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="namespaceURI" - type="j2ee:xsdAnyURIType"> - <xsd:annotation> - <xsd:documentation> - - The namespaceURI element indicates a URI. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="parameter-modeType"> - <xsd:annotation> - <xsd:documentation> - - The parameter-mode element defines the mode of the parameter. - It can have only three values, IN, OUT, INOUT. - - Used in: java-xml-type-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="IN"/> - <xsd:enumeration value="OUT"/> - <xsd:enumeration value="INOUT"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="port-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The port-mapping defines the mapping of the WSDL port name attribute - to the Java name used to generate the Generated Service Interface - method get{java-name}. - - Used in: service-interface-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="port-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The port-mapping defines the mapping of the WSDL port name - attribute to the Java name used to generate the Generated - Service Interface method get{java-name}. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="java-port-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The java-port-name element is the string to use as the port - name in Java. It is used in generating the Generated - Service Interface method get{java-port-name}. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="qname-scopeType"> - <xsd:annotation> - <xsd:documentation> - - The qname-scope elements scopes the reference of a QName to the WSDL - element type it applies to. The value of qname-scope may be - simpleType, complexType, or element. - - Used in: java-xml-type-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="simpleType"/> - <xsd:enumeration value="complexType"/> - <xsd:enumeration value="element"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-endpoint-interface-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The service-endpoint-interface-mapping defines a tuple - to specify Service Endpoint Interfaces to - WSDL port types and WSDL bindings. - - An interface may be mapped to a port-type and binding multiple - times. This happens rarely. - - Used in: java-wsdl-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="service-endpoint-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The service-endpoint-interface element defines the Java - type for the endpoint interface. The name must be a fully - qualified class name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-port-type" - type="j2ee:xsdQNameType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-port-type element defines the wsdl port type - by a QNAME which uniquely identifies the port type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-binding" - type="j2ee:xsdQNameType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-binding element defines the wsdl binding - by a QNAME which uniquely identifies the binding. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="service-endpoint-method-mapping" - type="j2ee:service-endpoint-method-mappingType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-endpoint-method-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The service-endpoint-method-mapping element defines the mapping of - Java methods to operations (which are not uniquely qualified by - qnames). - - The wsdl-operation should be interpreted with respect to the - portType and binding in which this definition is embedded within. - See the definitions for service-endpoint-interface-mapping and - service-interface-mapping to acquire the proper context. The - wrapped-element indicator should only be specified when a WSDL - message wraps an element type. The wsdl-return-value-mapping is - not specified for one-way operations. - - Used in: service-endpoint-interface-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="java-method-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The java-method-name element defines the name of a Java method - within an interface. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-operation" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-operation element defines an operation within a WSDL - document. It must be interpreted with respect to a port type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wrapped-element" - type="j2ee:emptyType" - minOccurs="0" - maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The wrapped-element element is defined when a WSDL message - with a single part is used to wrap an element type and the - element's name matches the operation name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="method-param-parts-mapping" - type="j2ee:method-param-parts-mappingType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="wsdl-return-value-mapping" - type="j2ee:wsdl-return-value-mappingType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-interface-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The service-interface-mapping element defines how a Java type for - the service interface maps to a WSDL service. - - Used in: java-wsdl-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="service-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The service-interface element defines the Java type for the service. - For static services, it is javax.xml.rpc.Service interface. For - generated service, it would be the generated interface name. - - The name must be a fully qualified class name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-service-name" - type="j2ee:xsdQNameType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-service-name element defines the wsdl service name - by a QNAME which uniquely identifies the service. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="port-mapping" - type="j2ee:port-mappingType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="variable-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The variable-mapping element defines the correlation between a - Java class data member or JavaBeans property to an XML element - or attribute name of an XML root type. If the data-member - element is present, the Java variable name is a public data - member. If data-member is not present, the Java variable name - is a JavaBeans property. - - Used in: java-xml-type-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="java-variable-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The java-variable-name defines the name of a public data member or - JavaBeans property within a Java class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="data-member" - type="j2ee:emptyType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The data-member element is a boolean indicator that a Java - variable is a public data member and not a JavaBeans property. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:choice> - <xsd:element name="xml-attribute-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The xml-attribute-name element defines name attribute value - of a WSDL attribute element within a root type. The value - of an xml-attribute-name element must match the value of - the ref attribute if mapping an attribute reference. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="xml-element-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The xml-element-name element defines name attribute value of - a WSDL element within a root type. The value of an - xml-element-name element must match the value of the ref - attribute if mapping an element reference. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="xml-wildcard" - type="j2ee:emptyType"> - <xsd:annotation> - <xsd:documentation> - - The xml-wildcard element associates the variable-mapping with - an xsd:any element within a root type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="wsdl-message-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-message-mapping element defines the mapping to a - specific message and its part. Together they define uniquely - the mapping for a specific parameter. Parts within a message - context are uniquely identified with their names. - - The parameter-mode is defined by the mapping to indicate - whether the mapping will be IN, OUT, or INOUT.. The presence - of the soap-header element indicates that the parameter is - mapped to a soap header only. When absent, it means that the - wsdl-message is mapped to a Java parameter. The soap headers - are interpreted in the order they are provided in the mapping. - - Used in: method-param-parts-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="wsdl-message" - type="j2ee:wsdl-messageType"/> - <xsd:element name="wsdl-message-part-name" - type="j2ee:wsdl-message-part-nameType"/> - <xsd:element name="parameter-mode" - type="j2ee:parameter-modeType"/> - <xsd:element name="soap-header" - type="j2ee:emptyType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The soap-header element is a boolean element indicating that - a parameter is mapped to a SOAP header. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="wsdl-message-part-nameType"> - <xsd:annotation> - <xsd:documentation> - - Interpretation of the wsdl-message-part-name element depends on - whether or not wrapped-element has been defined in the - service-endpoint-method-mapping. If wrapped-element is not - specified, wsdl-message-part-name defines a WSDL message part. It - should always be interpreted with respect to a wsdl-message - element. If wrapped-element is specified, wsdl-message-part-name - refers to an element name of the element type. - - Used in: wsdl-message-mapping, wsdl-return-value-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="wsdl-messageType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-message element defines a WSDL message by a QNAME. - - Used in: wsdl-message-mapping, wsdl-return-value-mapping, - exception-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:xsdQNameType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="wsdl-return-value-mappingType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-return-value-mapping element defines the mapping for the - method's return value. It defines the mapping to a specific message - and its part. Together they define uniquely the mapping for a - specific parameter. Parts within a message context are uniquely - identified with their names. The wsdl-message-part-name is not - specified if there is no return value or OUT parameters. - - Used in: service-endpoint-method-mapping - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="method-return-value" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The method-return-value element defines a fully qualified - class name or void type for the method's return value - type. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-message" - type="j2ee:wsdl-messageType"/> - <xsd:element name="wsdl-message-part-name" - type="j2ee:wsdl-message-part-nameType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_1_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_1_1.xsd deleted file mode 100644 index 7e2a7980a2..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_1_1.xsd +++ /dev/null @@ -1,491 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.1"> - <xsd:annotation> - <xsd:documentation> - @(#)j2ee_web_services_1_1.xsds 1.11 02/11/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - (C) Copyright International Business Machines Corporation 2002 - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The webservices element is the root element for the web services - deployment descriptor. It specifies the set of web service - descriptions that are to be deployed into the J2EE Application - Server and the dependencies they have on container resources and - services. The deployment descriptor must be named - "META-INF/webservices.xml" in the web services' jar file. - - Used in: webservices.xml - - All webservices deployment descriptors must indicate the - webservices schema by using the J2EE namespace: - - http://java.sun.com/xml/ns/j2ee - - and by indicating the version of the schema by using the version - element as shown below: - - <webservices xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee - http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd" - version="1.1"> - ... - </webservices> - - The instance documents may indicate the published version of the - schema using the xsi:schemaLocation attribute for the J2EE - namespace with the following location: - - http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="webservices" type="j2ee:webservicesType"> - <xsd:annotation> - <xsd:documentation> - - The webservices element is the root element for the web services - deployment descriptor. It specifies the set of web service - descriptions that are to be deployed into the J2EE Application Server - and the dependencies they have on container resources and services. - - Used in: webservices.xml - - </xsd:documentation> - </xsd:annotation> - - <xsd:key name="webservice-description-name-key"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description-name identifies the collection of - port-components associated with a WSDL file and JAX-RPC mapping. The - name must be unique within the deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:webservice-description"/> - <xsd:field xpath="j2ee:webservice-description-name"/> - </xsd:key> - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="port-componentType"> - <xsd:annotation> - <xsd:documentation> - - The port-component element associates a WSDL port with a web service - interface and implementation. It defines the name of the port as a - component, optional description, optional display name, optional iconic - representations, WSDL port QName, Service Endpoint Interface, Service - Implementation Bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="display-name" - type="j2ee:display-nameType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="icon" - type="j2ee:iconType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="port-component-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The port-component-name element specifies a port component's - name. This name is assigned by the module producer to name - the service implementation bean in the module's deployment - descriptor. The name must be unique among the port component - names defined in the same module. - - Used in: port-component - - Example: - <port-component-name>EmployeeService - </port-component-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-port" - type="j2ee:xsdQNameType"> - <xsd:annotation> - <xsd:documentation> - - Defines the name space and local name part of the WSDL port QName. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="service-endpoint-interface" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The service-endpoint-interface element contains the - fully-qualified name of the port component's Service Endpoint - Interface. - - Used in: port-component - - Example: - <remote>com.wombat.empl.EmployeeService</remote> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="service-impl-bean" - type="j2ee:service-impl-beanType"/> - - <xsd:element name="handler" - type="j2ee:port-component_handlerType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="port-component_handlerType"> - <xsd:annotation> - <xsd:documentation> - - Declares the handler for a port-component. Handlers can access the - init-param name/value pairs using the HandlerInfo interface. - - Used in: port-component - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="handler-name" - type="j2ee:string"> - <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:element name="handler-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines a fully qualified class name for the handler implementation. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="j2ee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - - <xsd:element name="soap-header" - type="j2ee:xsdQNameType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="soap-role" - type="j2ee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-impl-beanType"> - <xsd:annotation> - <xsd:documentation> - - The service-impl-bean element defines the web service implementation. - A service implementation can be an EJB bean class or JAX-RPC web - component. Existing EJB implementations are exposed as a web service - using an ejb-link. - - Used in: port-component - - </xsd:documentation> - </xsd:annotation> - <xsd:choice> - <xsd:element name="ejb-link" - type="j2ee:ejb-linkType"/> - <xsd:element name="servlet-link" - type="j2ee:servlet-linkType"/> - </xsd:choice> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-linkType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The servlet-link element is used in the service-impl-bean element - to specify that a Service Implementation Bean is defined as a - JAX-RPC Service Endpoint. - - The value of the servlet-link element must be the servlet-name of - a JAX-RPC Service Endpoint in the same WAR file. - - Used in: service-impl-bean - - Example: - <servlet-link>StockQuoteService</servlet-link> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webservice-descriptionType"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description element defines a WSDL document file - and the set of Port components associated with the WSDL ports - defined in the WSDL document. There may be multiple - webservice-descriptions defined within a module. - - All WSDL file ports must have a corresponding port-component element - defined. - - Used in: webservices - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="display-name" - type="j2ee:display-nameType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="icon" - type="j2ee:iconType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="webservice-description-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description-name identifies the collection of - port-components associated with a WSDL file and JAX-RPC - mapping. The name must be unique within the deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-file" - type="j2ee:pathType"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-file element contains the name of a WSDL file in the - module. The file name is a relative path within the module. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="jaxrpc-mapping-file" - type="j2ee:pathType"> - <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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="port-component" - type="j2ee:port-componentType" - minOccurs="1" maxOccurs="unbounded"> - <xsd:key name="port-component_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="j2ee:handler"/> - <xsd:field xpath="j2ee:handler-name"/> - </xsd:key> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webservicesType"> - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="webservice-description" - type="j2ee:webservice-descriptionType" - minOccurs="1" maxOccurs="unbounded"> - <xsd:key name="port-component-name-key"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The port-component-name element specifies a port - component's name. This name is assigned by the module - producer to name the service implementation bean in the - module's deployment descriptor. The name must be unique - among the port component names defined in the same module. - - Used in: port-component - - Example: - <port-component-name>EmployeeService - </port-component-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:port-component"/> - <xsd:field xpath="j2ee:port-component-name"/> - </xsd:key> - </xsd:element> - </xsd:sequence> - - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="1.1" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 1.1. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_client_1_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_client_1_1.xsd deleted file mode 100644 index 454a554528..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/j2ee_web_services_client_1_1.xsd +++ /dev/null @@ -1,345 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.1"> - <xsd:annotation> - <xsd:documentation> - @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - (C) Copyright International Business Machines Corporation 2002 - - </xsd:documentation> - </xsd:annotation> - - -<!-- **************************************************** --> - - <xsd:complexType name="port-component-refType"> - <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:element name="service-endpoint-interface" - type="j2ee:fully-qualified-classType"> - <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:element name="port-component-link" - type="j2ee:string" - minOccurs="0" maxOccurs="1"> - <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:group name="service-refGroup"> - <xsd:sequence> - <xsd:element name="service-ref" - type="j2ee:service-refType" - minOccurs="0" maxOccurs="unbounded"> - <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="j2ee:handler"/> - <xsd:field xpath="j2ee:handler-name"/> - </xsd:key> - </xsd:element> - </xsd:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="service-refType"> - <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:group ref="j2ee:descriptionGroup"/> - <xsd:element name="service-ref-name" - type="j2ee:jndi-nameType"> - <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:element name="service-interface" - type="j2ee:fully-qualified-classType"> - <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:element name="wsdl-file" - type="j2ee:xsdAnyURIType" - minOccurs="0" maxOccurs="1"> - <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:element name="jaxrpc-mapping-file" - type="j2ee:pathType" - minOccurs="0" maxOccurs="1"> - <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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="service-qname" - type="j2ee:xsdQNameType" - minOccurs="0" maxOccurs="1"> - <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:element name="port-component-ref" - type="j2ee:port-component-refType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="handler" - type="j2ee:service-ref_handlerType" - minOccurs="0" maxOccurs="unbounded"> - <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. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-ref_handlerType"> - <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:group ref="j2ee:descriptionGroup"/> - <xsd:element name="handler-name" - type="j2ee:string"> - <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:element name="handler-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines a fully qualified class name for the handler - implementation. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="j2ee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - - <xsd:element name="soap-header" - type="j2ee:xsdQNameType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="soap-role" - type="j2ee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="port-name" - type="j2ee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_5.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_5.xsd deleted file mode 100644 index db1018188e..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_5.xsd +++ /dev/null @@ -1,2096 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xsd:schema - 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> - @(#)javaee_5.xsds 1.65 06/02/17 - </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> - -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:import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2001/xml.xsd"/> - - <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/> - - -<!-- **************************************************** --> - - <xsd:group name="descriptionGroup"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="display-name" - type="javaee:display-nameType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="icon" - type="javaee:iconType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="descriptionType"> - <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 base="javaee:xsdStringType"> - <xsd:attribute ref="xml:lang"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="dewey-versionType"> - <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:complexType name="display-nameType"> - <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 base="javaee:string"> - <xsd:attribute ref="xml:lang"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-linkType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-local-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-ref-name" - type="javaee:ejb-ref-nameType"/> - <xsd:element name="ejb-ref-type" - type="javaee:ejb-ref-typeType" - minOccurs="0"/> - <xsd:element name="local-home" - type="javaee:local-homeType" - minOccurs="0"/> - <xsd:element name="local" - type="javaee:localType" - minOccurs="0"/> - <xsd:element name="ejb-link" - type="javaee:ejb-linkType" - minOccurs="0"/> - <xsd:group ref="javaee:resourceGroup"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-ref-nameType"> - <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:restriction base="javaee:jndi-nameType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-ref-typeType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="Entity"/> - <xsd:enumeration value="Session"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="ejb-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="ejb-ref-name" - type="javaee:ejb-ref-nameType"/> - <xsd:element name="ejb-ref-type" - type="javaee:ejb-ref-typeType" - minOccurs="0"/> - <xsd:element name="home" - type="javaee:homeType" - minOccurs="0"/> - <xsd:element name="remote" - type="javaee:remoteType" - minOccurs="0"/> - <xsd:element name="ejb-link" - type="javaee:ejb-linkType" - minOccurs="0"/> - <xsd:group ref="javaee:resourceGroup"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="emptyType"> - <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:complexType name="env-entry-type-valuesType"> - <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:restriction base="javaee:string"> - <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:complexType name="env-entryType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="env-entry-name" - type="javaee:jndi-nameType"> - <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:element name="env-entry-type" - type="javaee:env-entry-type-valuesType" - minOccurs="0"> - <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:element name="env-entry-value" - type="javaee:xsdStringType" - minOccurs="0"> - <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:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="fully-qualified-classType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="generic-booleanType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="true"/> - <xsd:enumeration value="false"/> - <xsd:enumeration value="yes"/> - <xsd:enumeration value="no"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="homeType"> - <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:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="iconType"> - <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:element name="small-icon" type="javaee:pathType" - minOccurs="0"> - <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:element name="large-icon" type="javaee:pathType" - minOccurs="0"> - <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 ref="xml:lang"/> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="injection-targetType"> - <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:element name="injection-target-class" - type="javaee:fully-qualified-classType"/> - <xsd:element name="injection-target-name" - type="javaee:java-identifierType"/> - </xsd:sequence> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-identifierType"> - <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:restriction base="javaee:string"> - <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="java-typeType"> - <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:restriction base="javaee:string"> - <xsd:pattern value="[^\p{Z}]*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jndi-nameType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:group name="jndiEnvironmentRefsGroup"> - <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: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:element name="ejb-local-ref" - type="javaee:ejb-local-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-context-ref" - type="javaee:persistence-context-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:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="lifecycle-callbackType"> - <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:element name="lifecycle-callback-class" - type="javaee:fully-qualified-classType" - minOccurs="0"/> - <xsd:element name="lifecycle-callback-method" - type="javaee:java-identifierType"/> - </xsd:sequence> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="listenerType"> - <xsd:annotation> - <xsd:documentation> - - The listenerType indicates the deployment properties for a web - application listener bean. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="listener-class" - type="javaee:fully-qualified-classType"> - <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:complexType name="local-homeType"> - <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:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="localType"> - <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:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-linkType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="message-destination-ref-name" - type="javaee:jndi-nameType"> - <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:element name="message-destination-type" - type="javaee:message-destination-typeType" - minOccurs="0"/> - <xsd:element name="message-destination-usage" - type="javaee:message-destination-usageType" - minOccurs="0"/> - <xsd:element name="message-destination-link" - type="javaee:message-destination-linkType" - minOccurs="0"/> - - <xsd:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-typeType"> - <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:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destination-usageType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="Consumes"/> - <xsd:enumeration value="Produces"/> - <xsd:enumeration value="ConsumesProduces"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="message-destinationType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="message-destination-name" - type="javaee:string"> - <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:element name="mapped-name" - type="javaee:xsdStringType" - minOccurs="0"> - <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:complexType name="param-valueType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="param-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The param-name element contains the name of a - parameter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="param-value" - type="javaee:xsdStringType"> - <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:complexType name="pathType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="persistence-context-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="persistence-context-ref-name" - type="javaee:jndi-nameType"> - <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:element name="persistence-unit-name" - type="javaee:string" - minOccurs="0"> - <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:element name="persistence-context-type" - type="javaee:persistence-context-typeType" - minOccurs="0"/> - - <xsd:element name="persistence-property" - type="javaee:propertyType" - minOccurs="0" - maxOccurs="unbounded"> - <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:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="persistence-context-typeType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="Transaction"/> - <xsd:enumeration value="Extended"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="persistence-unit-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="persistence-unit-ref-name" - type="javaee:jndi-nameType"> - <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:element name="persistence-unit-name" - type="javaee:string" - minOccurs="0"> - <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:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="propertyType"> - <xsd:annotation> - <xsd:documentation> - - Specifies a name/value pair. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="name" - type="javaee:xsdStringType"> - </xsd:element> - <xsd:element name="value" - type="javaee:xsdStringType"> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="remoteType"> - <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:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="res-authType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="Application"/> - <xsd:enumeration value="Container"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="res-sharing-scopeType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="Shareable"/> - <xsd:enumeration value="Unshareable"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="resource-env-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="resource-env-ref-name" - type="javaee:jndi-nameType"> - <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:element name="resource-env-ref-type" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <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:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="resource-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="res-ref-name" - type="javaee:jndi-nameType"> - <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:element name="res-type" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <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:element name="res-auth" - type="javaee:res-authType" - minOccurs="0"/> - - <xsd:element name="res-sharing-scope" - type="javaee:res-sharing-scopeType" - minOccurs="0"/> - - <xsd:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:group name="resourceGroup"> - <xsd:annotation> - <xsd:documentation> - - This group collects elements that are common to all the - JNDI resource elements. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="mapped-name" - type="javaee:xsdStringType" - minOccurs="0"> - <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:element name="injection-target" - type="javaee:injection-targetType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:group> - -<!-- **************************************************** --> - - <xsd:complexType name="role-nameType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="run-asType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="javaee:role-nameType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-role-refType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="javaee:role-nameType"> - <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:element name="role-link" - type="javaee:role-nameType" - minOccurs="0"> - <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:complexType name="security-roleType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="javaee:role-nameType"/> - </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:complexType name="true-falseType"> - <xsd:annotation> - <xsd:documentation> - - This simple type designates a boolean with only two - permissible values - - - true - - false - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:xsdBooleanType"> - <xsd:pattern value="(true|false)"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="url-patternType"> - <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:complexType name="xsdAnyURIType"> - <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:complexType name="xsdBooleanType"> - <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:complexType name="xsdIntegerType"> - <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:complexType name="xsdNMTOKENType"> - <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:complexType name="xsdNonNegativeIntegerType"> - <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:complexType name="xsdPositiveIntegerType"> - <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:complexType name="xsdQNameType"> - <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:complexType name="xsdStringType"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_1_2.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_1_2.xsd deleted file mode 100644 index e28cb1cefb..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_1_2.xsd +++ /dev/null @@ -1,747 +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="1.2"> - <xsd:annotation> - <xsd:documentation> - @(#)javaee_web_services_1_2.xsds 1.18 02/13/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> - - (C) Copyright International Business Machines Corporation 2002 - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The webservices element is the root element for the web services - deployment descriptor. It specifies the set of web service - descriptions that are to be deployed into the Java EE Application - Server and the dependencies they have on container resources and - services. The deployment descriptor must be named - "META-INF/webservices.xml" in the web services' jar file. - - Used in: webservices.xml - - All webservices deployment descriptors must indicate the - webservices 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: - - <webservices 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/javaee_web_services_1_2.xsd" - version="1.2"> - ... - </webservices> - - The instance documents may indicate the published version of the - schema using the xsi:schemaLocation attribute for the Java EE - namespace with the following location: - - http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.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="webservices" type="javaee:webservicesType"> - <xsd:annotation> - <xsd:documentation> - - The webservices element is the root element for the web services - deployment descriptor. It specifies the set of web service - descriptions that are to be deployed into the Java EE Application Server - and the dependencies they have on container resources and services. - - Used in: webservices.xml - - </xsd:documentation> - </xsd:annotation> - - <xsd:key name="webservice-description-name-key"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description-name identifies the collection of - port-components associated with a WSDL file and JAX-RPC mapping. The - name must be unique within the deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:webservice-description"/> - <xsd:field xpath="javaee:webservice-description-name"/> - </xsd:key> - </xsd:element> - -<!-- **************************************************** --> - - <xsd:complexType name="handler-chainType"> - <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 minOccurs="0" maxOccurs="1"> - <xsd:element name="service-name-pattern" - type="javaee:qname-pattern" /> - <xsd:element name="port-name-pattern" - type="javaee:qname-pattern" /> - <xsd:element name="protocol-bindings" - type="javaee:protocol-bindingListType"/> - </xsd:choice> - - <xsd:element name="handler" - type="javaee:port-component_handlerType" - minOccurs="1" maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="handler-chainsType"> - <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:element name="handler-chain" - type="javaee:handler-chainType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="port-componentType"> - <xsd:annotation> - <xsd:documentation> - - The port-component element associates a WSDL port with a web service - interface and implementation. It defines the name of the port as a - component, optional description, optional display name, optional iconic - representations, WSDL port QName, Service Endpoint Interface, Service - Implementation Bean. - - This element also associates a WSDL service with a JAX-WS Provider - implementation. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="display-name" - type="javaee:display-nameType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="icon" - type="javaee:iconType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="port-component-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The port-component-name element specifies a port component's - name. This name is assigned by the module producer to name - the service implementation bean in the module's deployment - descriptor. The name must be unique among the port component - names defined in the same module. - - Used in: port-component - - Example: - <port-component-name>EmployeeService - </port-component-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-service" - type="javaee:xsdQNameType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - Defines the name space and local name part of the WSDL - service QName. This is required to be specified for - port components that are JAX-WS Provider implementations. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-port" - type="javaee:xsdQNameType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - Defines the name space and local name part of the WSDL - port QName. This is not required to be specified for port - components that are JAX-WS Provider implementations - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="enable-mtom" - type="javaee:true-falseType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - Used to enable or disable SOAP MTOM/XOP mechanism for an - endpoint implementation. - - Not to be specified for JAX-RPC runtime - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="protocol-binding" - type="javaee:protocol-bindingType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - Used to specify the protocol binding used by the port-component. - If this element is not specified, then the default binding is - used (SOAP 1.1 over HTTP) - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="service-endpoint-interface" - type="javaee:fully-qualified-classType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The service-endpoint-interface element contains the - fully-qualified name of the port component's Service Endpoint - Interface. - - Used in: port-component - - Example: - <remote>com.wombat.empl.EmployeeService</remote> - - This may not be specified in case there is no Service - Enpoint Interface as is the case with directly using an - implementation class with the @WebService annotation. - - When the port component is a Provider implementation - this is not specified. - - ]]> - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="service-impl-bean" - type="javaee:service-impl-beanType"/> - - <xsd:choice> - <xsd:element name="handler" - type="javaee:port-component_handlerType" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - To be used with JAX-RPC based runtime only. - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="handler-chains" - type="javaee:handler-chainsType" - minOccurs="0" maxOccurs="1"> - <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:complexType name="port-component_handlerType"> - <xsd:annotation> - <xsd:documentation> - - Declares the handler for a port-component. Handlers can access the - init-param name/value pairs using the HandlerInfo interface. - - Used in: port-component - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="handler-name" - type="javaee:string"> - <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:element name="handler-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines a fully qualified class name for the handler implementation. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="javaee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - - <xsd:element name="soap-header" - type="javaee:xsdQNameType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="soap-role" - type="javaee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="protocol-URIAliasType"> - <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:simpleType name="protocol-bindingListType"> - <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:list itemType="javaee:protocol-bindingType"/> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:simpleType name="protocol-bindingType"> - <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:union memberTypes="xsd:anyURI javaee:protocol-URIAliasType"/> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:simpleType name="qname-pattern"> - <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:complexType name="service-impl-beanType"> - <xsd:annotation> - <xsd:documentation> - - The service-impl-bean element defines the web service implementation. - A service implementation can be an EJB bean class or JAX-RPC web - component. Existing EJB implementations are exposed as a web service - using an ejb-link. - - Used in: port-component - - </xsd:documentation> - </xsd:annotation> - <xsd:choice> - <xsd:element name="ejb-link" - type="javaee:ejb-linkType"/> - <xsd:element name="servlet-link" - type="javaee:servlet-linkType"/> - </xsd:choice> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-linkType"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The servlet-link element is used in the service-impl-bean element - to specify that a Service Implementation Bean is defined as a - JAX-RPC Service Endpoint. - - The value of the servlet-link element must be the servlet-name of - a JAX-RPC Service Endpoint in the same WAR file. - - Used in: service-impl-bean - - Example: - <servlet-link>StockQuoteService</servlet-link> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webservice-descriptionType"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description element defines a WSDL document file - and the set of Port components associated with the WSDL ports - defined in the WSDL document. There may be multiple - webservice-descriptions defined within a module. - - All WSDL file ports must have a corresponding port-component element - defined. - - Used in: webservices - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="display-name" - type="javaee:display-nameType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="icon" - type="javaee:iconType" - minOccurs="0" maxOccurs="1"/> - <xsd:element name="webservice-description-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The webservice-description-name identifies the collection of - port-components associated with a WSDL file and JAX-RPC - mapping. The name must be unique within the deployment descriptor. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="wsdl-file" - type="javaee:pathType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - - The wsdl-file element contains the name of a WSDL file in the - module. The file name is a relative path within the module. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="jaxrpc-mapping-file" - type="javaee:pathType" - minOccurs="0" maxOccurs="1"> - <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. - - This is not required when JAX-WS based runtime is used. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="port-component" - type="javaee:port-componentType" - minOccurs="1" maxOccurs="unbounded"> - <xsd:key name="port-component_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:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="webservicesType"> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="webservice-description" - type="javaee:webservice-descriptionType" - minOccurs="1" maxOccurs="unbounded"> - <xsd:key name="port-component-name-key"> - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - The port-component-name element specifies a port - component's name. This name is assigned by the module - producer to name the service implementation bean in the - module's deployment descriptor. The name must be unique - among the port component names defined in the same module. - - Used in: port-component - - Example: - <port-component-name>EmployeeService - </port-component-name> - - ]]> - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:port-component"/> - <xsd:field xpath="javaee:port-component-name"/> - </xsd:key> - </xsd:element> - </xsd:sequence> - - <xsd:attribute name="version" - type="javaee:dewey-versionType" - fixed="1.2" - use="required"> - <xsd:annotation> - <xsd:documentation> - - The required value for the version is 1.2. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_client_1_2.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_client_1_2.xsd deleted file mode 100644 index 3df0dd6279..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/javaee_web_services_client_1_2.xsd +++ /dev/null @@ -1,578 +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="1.2"> - <xsd:annotation> - <xsd:documentation> - @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/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> - - (C) Copyright International Business Machines Corporation 2002 - - </xsd:documentation> - </xsd:annotation> - - -<!-- **************************************************** --> - - <xsd:complexType name="port-component-refType"> - <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:element name="service-endpoint-interface" - type="javaee:fully-qualified-classType"> - <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:element name="enable-mtom" - type="javaee:true-falseType" - minOccurs="0" maxOccurs="1"> - <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:element name="port-component-link" - type="javaee:string" - minOccurs="0" maxOccurs="1"> - <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:group name="service-refGroup"> - <xsd:sequence> - <xsd:element name="service-ref" - type="javaee:service-refType" - minOccurs="0" maxOccurs="unbounded"> - <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:complexType name="service-refType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="service-ref-name" - type="javaee:jndi-nameType"> - <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:element name="service-interface" - type="javaee:fully-qualified-classType"> - <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:element name="service-ref-type" - type="javaee:fully-qualified-classType" - minOccurs="0" maxOccurs="1"> - <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:element name="wsdl-file" - type="javaee:xsdAnyURIType" - minOccurs="0" maxOccurs="1"> - <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:element name="jaxrpc-mapping-file" - type="javaee:pathType" - minOccurs="0" maxOccurs="1"> - <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:element name="service-qname" - type="javaee:xsdQNameType" - minOccurs="0" maxOccurs="1"> - <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:element name="port-component-ref" - type="javaee:port-component-refType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="handler" - type="javaee:service-ref_handlerType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="handler-chains" - type="javaee:service-ref_handler-chainsType" - minOccurs="0" maxOccurs="1"> - <xsd:annotation> - <xsd:documentation> - To be used with JAX-WS based runtime only. - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - - <xsd:group ref="javaee:resourceGroup"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-ref_handler-chainType"> - <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 minOccurs="0" maxOccurs="1"> - <xsd:element name="service-name-pattern" - type="javaee:service-ref_qname-pattern" /> - <xsd:element name="port-name-pattern" - type="javaee:service-ref_qname-pattern" /> - <xsd:element name="protocol-bindings" - type="javaee:service-ref_protocol-bindingListType"/> - </xsd:choice> - - <xsd:element name="handler" - type="javaee:service-ref_handlerType" - minOccurs="1" maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-ref_handler-chainsType"> - <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:element name="handler-chain" - type="javaee:service-ref_handler-chainType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="service-ref_handlerType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="handler-name" - type="javaee:string"> - <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:element name="handler-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines a fully qualified class name for the handler - implementation. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="javaee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - - <xsd:element name="soap-header" - type="javaee:xsdQNameType" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="soap-role" - type="javaee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:element name="port-name" - type="javaee:string" - minOccurs="0" maxOccurs="unbounded"> - <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:simpleType name="service-ref_protocol-URIAliasType"> - <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:simpleType name="service-ref_protocol-bindingListType"> - <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:list itemType="javaee:service-ref_protocol-bindingType"/> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:simpleType name="service-ref_protocol-bindingType"> - <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:union memberTypes="xsd:anyURI javaee:service-ref_protocol-URIAliasType"/> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:simpleType name="service-ref_qname-pattern"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_0.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_0.xsd deleted file mode 100644 index 970a76d7df..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_0.xsd +++ /dev/null @@ -1,308 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="2.0"> - <xsd:annotation> - <xsd:documentation> - @(#)jsp_2_0.xsds 1.17 03/18/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - This is the XML Schema for the JSP 2.0 deployment descriptor - types. The JSP 2.0 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_4.xsd - file to define JSP specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-configType"> - <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:element name="taglib" - type="j2ee:taglibType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="jsp-property-group" - type="j2ee:jsp-property-groupType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-fileType"> - <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:restriction base="j2ee:pathType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-property-groupType"> - <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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="url-pattern" - type="j2ee:url-patternType" - maxOccurs="unbounded"/> - <xsd:element name="el-ignored" - type="j2ee:true-falseType" - minOccurs="0"> - <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:element name="page-encoding" - type="j2ee:string" - minOccurs="0"> - <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:element name="scripting-invalid" - type="j2ee:true-falseType" - minOccurs="0"> - <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:element name="is-xml" - type="j2ee:true-falseType" - minOccurs="0"> - <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:element name="include-prelude" - type="j2ee:pathType" - minOccurs="0" - maxOccurs="unbounded"> - <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:element name="include-coda" - type="j2ee:pathType" - minOccurs="0" - maxOccurs="unbounded"> - <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:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="taglibType"> - <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:element name="taglib-uri" - type="j2ee:string"> - <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:element name="taglib-location" - type="j2ee:pathType"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_1.xsd deleted file mode 100644 index ab633886d9..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/jsp_2_1.xsd +++ /dev/null @@ -1,343 +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="2.1"> - <xsd:annotation> - <xsd:documentation> - @(#)jsp_2_1.xsds 1.5 08/11/05 - </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> - - 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:include schemaLocation="javaee_5.xsd"/> - - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-configType"> - <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:element name="taglib" - type="javaee:taglibType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="jsp-property-group" - type="javaee:jsp-property-groupType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-fileType"> - <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:restriction base="javaee:pathType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="jsp-property-groupType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="url-pattern" - type="javaee:url-patternType" - maxOccurs="unbounded"/> - <xsd:element name="el-ignored" - type="javaee:true-falseType" - minOccurs="0"> - <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:element name="page-encoding" - type="javaee:string" - minOccurs="0"> - <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:element name="scripting-invalid" - type="javaee:true-falseType" - minOccurs="0"> - <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:element name="is-xml" - type="javaee:true-falseType" - minOccurs="0"> - <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:element name="include-prelude" - type="javaee:pathType" - minOccurs="0" - maxOccurs="unbounded"> - <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:element name="include-coda" - type="javaee:pathType" - minOccurs="0" - maxOccurs="unbounded"> - <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:element name="deferred-syntax-allowed-as-literal" - type="javaee:true-falseType" - minOccurs="0"> - <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:element name="trim-directive-whitespaces" - type="javaee:true-falseType" - minOccurs="0"> - <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:complexType name="taglibType"> - <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:element name="taglib-uri" - type="javaee:string"> - <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:element name="taglib-location" - type="javaee:pathType"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/orm_1_0.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/orm_1_0.xsd deleted file mode 100644 index bfd9c7540d..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/orm_1_0.xsd +++ /dev/null @@ -1,1562 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!-- Java Persistence API object-relational mapping file schema --> -<xsd:schema targetNamespace="http://java.sun.com/xml/ns/persistence/orm" - xmlns:orm="http://java.sun.com/xml/ns/persistence/orm" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.0"> - - <xsd:annotation> - <xsd:documentation> - @(#)orm_1_0.xsd 1.0 Feb 14 2006 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. - - Copyright 2005-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. - - The Eclipse Foundation elects to include this software in this - distribution under the CDDL license. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation><![CDATA[ - - This is the XML Schema for the persistence object-relational - mapping file. - The file may be named "META-INF/orm.xml" in the persistence - archive or it may be named some other name which would be - used to locate the file as resource on the classpath. - - ]]></xsd:documentation> - </xsd:annotation> - - <xsd:complexType name="emptyType"/> - - <xsd:simpleType name="versionType"> - <xsd:restriction base="xsd:token"> - <xsd:pattern value="[0-9]+(\.[0-9]+)*"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:element name="entity-mappings"> - <xsd:complexType> - <xsd:annotation> - <xsd:documentation> - - The entity-mappings element is the root element of an mapping - file. It contains the following four types of elements: - - 1. The persistence-unit-metadata element contains metadata - for the entire persistence unit. It is undefined if this element - occurs in multiple mapping files within the same persistence unit. - - 2. The package, schema, catalog and access elements apply to all of - the entity, mapped-superclass and embeddable elements defined in - the same file in which they occur. - - 3. The sequence-generator, table-generator, named-query, - named-native-query and sql-result-set-mapping elements are global - to the persistence unit. It is undefined to have more than one - sequence-generator or table-generator of the same name in the same - or different mapping files in a persistence unit. It is also - undefined to have more than one named-query or named-native-query - of the same name in the same or different mapping files in a - persistence unit. - - 4. The entity, mapped-superclass and embeddable elements each define - the mapping information for a managed persistent class. The mapping - information contained in these elements may be complete or it may - be partial. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" type="xsd:string" - minOccurs="0"/> - <xsd:element name="persistence-unit-metadata" - type="orm:persistence-unit-metadata" - minOccurs="0"/> - <xsd:element name="package" type="xsd:string" - minOccurs="0"/> - <xsd:element name="schema" type="xsd:string" - minOccurs="0"/> - <xsd:element name="catalog" type="xsd:string" - minOccurs="0"/> - <xsd:element name="access" type="orm:access-type" - minOccurs="0"/> - <xsd:element name="sequence-generator" type="orm:sequence-generator" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="table-generator" type="orm:table-generator" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="named-query" type="orm:named-query" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="named-native-query" type="orm:named-native-query" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="sql-result-set-mapping" - type="orm:sql-result-set-mapping" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="mapped-superclass" type="orm:mapped-superclass" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="entity" type="orm:entity" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="embeddable" type="orm:embeddable" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="version" type="orm:versionType" - fixed="1.0" use="required"/> - </xsd:complexType> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:complexType name="persistence-unit-metadata"> - <xsd:annotation> - <xsd:documentation> - - Metadata that applies to the persistence unit and not just to - the mapping file in which it is contained. - - If the xml-mapping-metadata-complete element is specified then - the complete set of mapping metadata for the persistence unit - is contained in the XML mapping files for the persistence unit. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="xml-mapping-metadata-complete" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="persistence-unit-defaults" - type="orm:persistence-unit-defaults" - minOccurs="0"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="persistence-unit-defaults"> - <xsd:annotation> - <xsd:documentation> - - These defaults are applied to the persistence unit as a whole - unless they are overridden by local annotation or XML - element settings. - - schema - Used as the schema for all tables or secondary tables - that apply to the persistence unit - catalog - Used as the catalog for all tables or secondary tables - that apply to the persistence unit - access - Used as the access type for all managed classes in - the persistence unit - cascade-persist - Adds cascade-persist to the set of cascade options - in entity relationships of the persistence unit - entity-listeners - List of default entity listeners to be invoked - on each entity in the persistence unit. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="schema" type="xsd:string" - minOccurs="0"/> - <xsd:element name="catalog" type="xsd:string" - minOccurs="0"/> - <xsd:element name="access" type="orm:access-type" - minOccurs="0"/> - <xsd:element name="cascade-persist" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="entity-listeners" type="orm:entity-listeners" - minOccurs="0"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="entity"> - <xsd:annotation> - <xsd:documentation> - - Defines the settings and mappings for an entity. Is allowed to be - sparsely populated and used in conjunction with the annotations. - Alternatively, the metadata-complete attribute can be used to - indicate that no annotations on the entity class (and its fields - or properties) are to be processed. If this is the case then - the defaulting rules for the entity and its subelements will - be recursively applied. - - @Target(TYPE) @Retention(RUNTIME) - public @interface Entity { - String name() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" type="xsd:string" minOccurs="0"/> - <xsd:element name="table" type="orm:table" - minOccurs="0"/> - <xsd:element name="secondary-table" type="orm:secondary-table" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="primary-key-join-column" - type="orm:primary-key-join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="id-class" type="orm:id-class" minOccurs="0"/> - <xsd:element name="inheritance" type="orm:inheritance" minOccurs="0"/> - <xsd:element name="discriminator-value" type="orm:discriminator-value" - minOccurs="0"/> - <xsd:element name="discriminator-column" - type="orm:discriminator-column" - minOccurs="0"/> - <xsd:element name="sequence-generator" type="orm:sequence-generator" - minOccurs="0"/> - <xsd:element name="table-generator" type="orm:table-generator" - minOccurs="0"/> - <xsd:element name="named-query" type="orm:named-query" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="named-native-query" type="orm:named-native-query" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="sql-result-set-mapping" - type="orm:sql-result-set-mapping" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="exclude-default-listeners" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="exclude-superclass-listeners" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="entity-listeners" type="orm:entity-listeners" - minOccurs="0"/> - <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/> - <xsd:element name="post-persist" type="orm:post-persist" - minOccurs="0"/> - <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/> - <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/> - <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/> - <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/> - <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/> - <xsd:element name="attribute-override" type="orm:attribute-override" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="association-override" - type="orm:association-override" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="attributes" type="orm:attributes" minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="class" type="xsd:string" use="required"/> - <xsd:attribute name="access" type="orm:access-type"/> - <xsd:attribute name="metadata-complete" type="xsd:boolean"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="attributes"> - <xsd:annotation> - <xsd:documentation> - - This element contains the entity field or property mappings. - It may be sparsely populated to include only a subset of the - fields or properties. If metadata-complete for the entity is true - then the remainder of the attributes will be defaulted according - to the default rules. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:choice> - <xsd:element name="id" type="orm:id" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="embedded-id" type="orm:embedded-id" - minOccurs="0"/> - </xsd:choice> - <xsd:element name="basic" type="orm:basic" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="version" type="orm:version" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="many-to-one" type="orm:many-to-one" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="one-to-many" type="orm:one-to-many" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="one-to-one" type="orm:one-to-one" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="many-to-many" type="orm:many-to-many" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="embedded" type="orm:embedded" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="transient" type="orm:transient" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="access-type"> - <xsd:annotation> - <xsd:documentation> - - This element determines how the persistence provider accesses the - state of an entity or embedded object. - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="PROPERTY"/> - <xsd:enumeration value="FIELD"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="entity-listeners"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface EntityListeners { - Class[] value(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="entity-listener" type="orm:entity-listener" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="entity-listener"> - <xsd:annotation> - <xsd:documentation> - - Defines an entity listener to be invoked at lifecycle events - for the entities that list this listener. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/> - <xsd:element name="post-persist" type="orm:post-persist" - minOccurs="0"/> - <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/> - <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/> - <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/> - <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/> - <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="class" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="pre-persist"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PrePersist {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="post-persist"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PostPersist {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="pre-remove"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PreRemove {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="post-remove"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PostRemove {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="pre-update"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PreUpdate {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="post-update"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PostUpdate {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="post-load"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD}) @Retention(RUNTIME) - public @interface PostLoad {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="method-name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="query-hint"> - <xsd:annotation> - <xsd:documentation> - - @Target({}) @Retention(RUNTIME) - public @interface QueryHint { - String name(); - String value(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="value" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="named-query"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface NamedQuery { - String name(); - String query(); - QueryHint[] hints() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="query" type="xsd:string"/> - <xsd:element name="hint" type="orm:query-hint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="named-native-query"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface NamedNativeQuery { - String name(); - String query(); - QueryHint[] hints() default {}; - Class resultClass() default void.class; - String resultSetMapping() default ""; //named SqlResultSetMapping - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="query" type="xsd:string"/> - <xsd:element name="hint" type="orm:query-hint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="result-class" type="xsd:string"/> - <xsd:attribute name="result-set-mapping" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="sql-result-set-mapping"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface SqlResultSetMapping { - String name(); - EntityResult[] entities() default {}; - ColumnResult[] columns() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="entity-result" type="orm:entity-result" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="column-result" type="orm:column-result" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="entity-result"> - <xsd:annotation> - <xsd:documentation> - - @Target({}) @Retention(RUNTIME) - public @interface EntityResult { - Class entityClass(); - FieldResult[] fields() default {}; - String discriminatorColumn() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="field-result" type="orm:field-result" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="entity-class" type="xsd:string" use="required"/> - <xsd:attribute name="discriminator-column" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="field-result"> - <xsd:annotation> - <xsd:documentation> - - @Target({}) @Retention(RUNTIME) - public @interface FieldResult { - String name(); - String column(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="column" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="column-result"> - <xsd:annotation> - <xsd:documentation> - - @Target({}) @Retention(RUNTIME) - public @interface ColumnResult { - String name(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="table"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface Table { - String name() default ""; - String catalog() default ""; - String schema() default ""; - UniqueConstraint[] uniqueConstraints() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="unique-constraint" type="orm:unique-constraint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="catalog" type="xsd:string"/> - <xsd:attribute name="schema" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="secondary-table"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface SecondaryTable { - String name(); - String catalog() default ""; - String schema() default ""; - PrimaryKeyJoinColumn[] pkJoinColumns() default {}; - UniqueConstraint[] uniqueConstraints() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="primary-key-join-column" - type="orm:primary-key-join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="unique-constraint" type="orm:unique-constraint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="catalog" type="xsd:string"/> - <xsd:attribute name="schema" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="unique-constraint"> - <xsd:annotation> - <xsd:documentation> - - @Target({}) @Retention(RUNTIME) - public @interface UniqueConstraint { - String[] columnNames(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="column-name" type="xsd:string" - maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="column"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Column { - String name() default ""; - boolean unique() default false; - boolean nullable() default true; - boolean insertable() default true; - boolean updatable() default true; - String columnDefinition() default ""; - String table() default ""; - int length() default 255; - int precision() default 0; // decimal precision - int scale() default 0; // decimal scale - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="unique" type="xsd:boolean"/> - <xsd:attribute name="nullable" type="xsd:boolean"/> - <xsd:attribute name="insertable" type="xsd:boolean"/> - <xsd:attribute name="updatable" type="xsd:boolean"/> - <xsd:attribute name="column-definition" type="xsd:string"/> - <xsd:attribute name="table" type="xsd:string"/> - <xsd:attribute name="length" type="xsd:int"/> - <xsd:attribute name="precision" type="xsd:int"/> - <xsd:attribute name="scale" type="xsd:int"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="join-column"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface JoinColumn { - String name() default ""; - String referencedColumnName() default ""; - boolean unique() default false; - boolean nullable() default true; - boolean insertable() default true; - boolean updatable() default true; - String columnDefinition() default ""; - String table() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="referenced-column-name" type="xsd:string"/> - <xsd:attribute name="unique" type="xsd:boolean"/> - <xsd:attribute name="nullable" type="xsd:boolean"/> - <xsd:attribute name="insertable" type="xsd:boolean"/> - <xsd:attribute name="updatable" type="xsd:boolean"/> - <xsd:attribute name="column-definition" type="xsd:string"/> - <xsd:attribute name="table" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="generation-type"> - <xsd:annotation> - <xsd:documentation> - - public enum GenerationType { TABLE, SEQUENCE, IDENTITY, AUTO }; - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="TABLE"/> - <xsd:enumeration value="SEQUENCE"/> - <xsd:enumeration value="IDENTITY"/> - <xsd:enumeration value="AUTO"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="attribute-override"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME) - public @interface AttributeOverride { - String name(); - Column column(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="column" type="orm:column"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="association-override"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME) - public @interface AssociationOverride { - String name(); - JoinColumn[] joinColumns(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="join-column" type="orm:join-column" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="id-class"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface IdClass { - Class value(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="class" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="id"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Id {} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="column" type="orm:column" - minOccurs="0"/> - <xsd:element name="generated-value" type="orm:generated-value" - minOccurs="0"/> - <xsd:element name="temporal" type="orm:temporal" - minOccurs="0"/> - <xsd:element name="table-generator" type="orm:table-generator" - minOccurs="0"/> - <xsd:element name="sequence-generator" type="orm:sequence-generator" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="embedded-id"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface EmbeddedId {} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="attribute-override" type="orm:attribute-override" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="transient"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Transient {} - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="version"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Version {} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="column" type="orm:column" minOccurs="0"/> - <xsd:element name="temporal" type="orm:temporal" minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="basic"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Basic { - FetchType fetch() default EAGER; - boolean optional() default true; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="column" type="orm:column" minOccurs="0"/> - <xsd:choice> - <xsd:element name="lob" type="orm:lob" minOccurs="0"/> - <xsd:element name="temporal" type="orm:temporal" minOccurs="0"/> - <xsd:element name="enumerated" type="orm:enumerated" minOccurs="0"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="fetch" type="orm:fetch-type"/> - <xsd:attribute name="optional" type="xsd:boolean"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="fetch-type"> - <xsd:annotation> - <xsd:documentation> - - public enum FetchType { LAZY, EAGER }; - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="LAZY"/> - <xsd:enumeration value="EAGER"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="lob"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Lob {} - - </xsd:documentation> - </xsd:annotation> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="temporal"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Temporal { - TemporalType value(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="orm:temporal-type"/> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:simpleType name="temporal-type"> - <xsd:annotation> - <xsd:documentation> - - public enum TemporalType { - DATE, // java.sql.Date - TIME, // java.sql.Time - TIMESTAMP // java.sql.Timestamp - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="DATE"/> - <xsd:enumeration value="TIME"/> - <xsd:enumeration value="TIMESTAMP"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:simpleType name="enumerated"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Enumerated { - EnumType value() default ORDINAL; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="orm:enum-type"/> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:simpleType name="enum-type"> - <xsd:annotation> - <xsd:documentation> - - public enum EnumType { - ORDINAL, - STRING - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="ORDINAL"/> - <xsd:enumeration value="STRING"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="many-to-one"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface ManyToOne { - Class targetEntity() default void.class; - CascadeType[] cascade() default {}; - FetchType fetch() default EAGER; - boolean optional() default true; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:choice> - <xsd:element name="join-column" type="orm:join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="join-table" type="orm:join-table" - minOccurs="0"/> - </xsd:choice> - <xsd:element name="cascade" type="orm:cascade-type" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="target-entity" type="xsd:string"/> - <xsd:attribute name="fetch" type="orm:fetch-type"/> - <xsd:attribute name="optional" type="xsd:boolean"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="cascade-type"> - <xsd:annotation> - <xsd:documentation> - - public enum CascadeType { ALL, PERSIST, MERGE, REMOVE, REFRESH}; - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="cascade-all" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="cascade-persist" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="cascade-merge" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="cascade-remove" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="cascade-refresh" type="orm:emptyType" - minOccurs="0"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="one-to-one"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface OneToOne { - Class targetEntity() default void.class; - CascadeType[] cascade() default {}; - FetchType fetch() default EAGER; - boolean optional() default true; - String mappedBy() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:choice> - <xsd:element name="primary-key-join-column" - type="orm:primary-key-join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="join-column" type="orm:join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="join-table" type="orm:join-table" - minOccurs="0"/> - </xsd:choice> - <xsd:element name="cascade" type="orm:cascade-type" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="target-entity" type="xsd:string"/> - <xsd:attribute name="fetch" type="orm:fetch-type"/> - <xsd:attribute name="optional" type="xsd:boolean"/> - <xsd:attribute name="mapped-by" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="one-to-many"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface OneToMany { - Class targetEntity() default void.class; - CascadeType[] cascade() default {}; - FetchType fetch() default LAZY; - String mappedBy() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="order-by" type="orm:order-by" - minOccurs="0"/> - <xsd:element name="map-key" type="orm:map-key" - minOccurs="0"/> - <xsd:choice> - <xsd:element name="join-table" type="orm:join-table" - minOccurs="0"/> - <xsd:element name="join-column" type="orm:join-column" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:choice> - <xsd:element name="cascade" type="orm:cascade-type" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="target-entity" type="xsd:string"/> - <xsd:attribute name="fetch" type="orm:fetch-type"/> - <xsd:attribute name="mapped-by" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="join-table"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface JoinTable { - String name() default ""; - String catalog() default ""; - String schema() default ""; - JoinColumn[] joinColumns() default {}; - JoinColumn[] inverseJoinColumns() default {}; - UniqueConstraint[] uniqueConstraints() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="join-column" type="orm:join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="inverse-join-column" type="orm:join-column" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="unique-constraint" type="orm:unique-constraint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="catalog" type="xsd:string"/> - <xsd:attribute name="schema" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="many-to-many"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface ManyToMany { - Class targetEntity() default void.class; - CascadeType[] cascade() default {}; - FetchType fetch() default LAZY; - String mappedBy() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="order-by" type="orm:order-by" - minOccurs="0"/> - <xsd:element name="map-key" type="orm:map-key" - minOccurs="0"/> - <xsd:element name="join-table" type="orm:join-table" - minOccurs="0"/> - <xsd:element name="cascade" type="orm:cascade-type" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="target-entity" type="xsd:string"/> - <xsd:attribute name="fetch" type="orm:fetch-type"/> - <xsd:attribute name="mapped-by" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="generated-value"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface GeneratedValue { - GenerationType strategy() default AUTO; - String generator() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="strategy" type="orm:generation-type"/> - <xsd:attribute name="generator" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="map-key"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface MapKey { - String name() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="order-by"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface OrderBy { - String value() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:string"/> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="inheritance"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface Inheritance { - InheritanceType strategy() default SINGLE_TABLE; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="strategy" type="orm:inheritance-type"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="inheritance-type"> - <xsd:annotation> - <xsd:documentation> - - public enum InheritanceType - { SINGLE_TABLE, JOINED, TABLE_PER_CLASS}; - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="SINGLE_TABLE"/> - <xsd:enumeration value="JOINED"/> - <xsd:enumeration value="TABLE_PER_CLASS"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:simpleType name="discriminator-value"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface DiscriminatorValue { - String value(); - } - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:string"/> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:simpleType name="discriminator-type"> - <xsd:annotation> - <xsd:documentation> - - public enum DiscriminatorType { STRING, CHAR, INTEGER }; - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="STRING"/> - <xsd:enumeration value="CHAR"/> - <xsd:enumeration value="INTEGER"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="primary-key-join-column"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME) - public @interface PrimaryKeyJoinColumn { - String name() default ""; - String referencedColumnName() default ""; - String columnDefinition() default ""; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="referenced-column-name" type="xsd:string"/> - <xsd:attribute name="column-definition" type="xsd:string"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="discriminator-column"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE}) @Retention(RUNTIME) - public @interface DiscriminatorColumn { - String name() default "DTYPE"; - DiscriminatorType discriminatorType() default STRING; - String columnDefinition() default ""; - int length() default 31; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string"/> - <xsd:attribute name="discriminator-type" type="orm:discriminator-type"/> - <xsd:attribute name="column-definition" type="xsd:string"/> - <xsd:attribute name="length" type="xsd:int"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="embeddable"> - <xsd:annotation> - <xsd:documentation> - - Defines the settings and mappings for embeddable objects. Is - allowed to be sparsely populated and used in conjunction with - the annotations. Alternatively, the metadata-complete attribute - can be used to indicate that no annotations are to be processed - in the class. If this is the case then the defaulting rules will - be recursively applied. - - @Target({TYPE}) @Retention(RUNTIME) - public @interface Embeddable {} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" type="xsd:string" minOccurs="0"/> - <xsd:element name="attributes" type="orm:embeddable-attributes" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="class" type="xsd:string" use="required"/> - <xsd:attribute name="access" type="orm:access-type"/> - <xsd:attribute name="metadata-complete" type="xsd:boolean"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="embeddable-attributes"> - <xsd:sequence> - <xsd:element name="basic" type="orm:basic" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="transient" type="orm:transient" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="embedded"> - <xsd:annotation> - <xsd:documentation> - - @Target({METHOD, FIELD}) @Retention(RUNTIME) - public @interface Embedded {} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="attribute-override" type="orm:attribute-override" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="mapped-superclass"> - <xsd:annotation> - <xsd:documentation> - - Defines the settings and mappings for a mapped superclass. Is - allowed to be sparsely populated and used in conjunction with - the annotations. Alternatively, the metadata-complete attribute - can be used to indicate that no annotations are to be processed - If this is the case then the defaulting rules will be recursively - applied. - - @Target(TYPE) @Retention(RUNTIME) - public @interface MappedSuperclass{} - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" type="xsd:string" minOccurs="0"/> - <xsd:element name="id-class" type="orm:id-class" minOccurs="0"/> - <xsd:element name="exclude-default-listeners" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="exclude-superclass-listeners" type="orm:emptyType" - minOccurs="0"/> - <xsd:element name="entity-listeners" type="orm:entity-listeners" - minOccurs="0"/> - <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/> - <xsd:element name="post-persist" type="orm:post-persist" - minOccurs="0"/> - <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/> - <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/> - <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/> - <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/> - <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/> - <xsd:element name="attributes" type="orm:attributes" minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="class" type="xsd:string" use="required"/> - <xsd:attribute name="access" type="orm:access-type"/> - <xsd:attribute name="metadata-complete" type="xsd:boolean"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="sequence-generator"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME) - public @interface SequenceGenerator { - String name(); - String sequenceName() default ""; - int initialValue() default 1; - int allocationSize() default 50; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="sequence-name" type="xsd:string"/> - <xsd:attribute name="initial-value" type="xsd:int"/> - <xsd:attribute name="allocation-size" type="xsd:int"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="table-generator"> - <xsd:annotation> - <xsd:documentation> - - @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME) - public @interface TableGenerator { - String name(); - String table() default ""; - String catalog() default ""; - String schema() default ""; - String pkColumnName() default ""; - String valueColumnName() default ""; - String pkColumnValue() default ""; - int initialValue() default 0; - int allocationSize() default 50; - UniqueConstraint[] uniqueConstraints() default {}; - } - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="unique-constraint" type="orm:unique-constraint" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="name" type="xsd:string" use="required"/> - <xsd:attribute name="table" type="xsd:string"/> - <xsd:attribute name="catalog" type="xsd:string"/> - <xsd:attribute name="schema" type="xsd:string"/> - <xsd:attribute name="pk-column-name" type="xsd:string"/> - <xsd:attribute name="value-column-name" type="xsd:string"/> - <xsd:attribute name="pk-column-value" type="xsd:string"/> - <xsd:attribute name="initial-value" type="xsd:int"/> - <xsd:attribute name="allocation-size" type="xsd:int"/> - </xsd:complexType> - -</xsd:schema>
\ No newline at end of file diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/persistence_1_0.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/persistence_1_0.xsd deleted file mode 100644 index a3a157d96e..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/persistence_1_0.xsd +++ /dev/null @@ -1,307 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!-- persistence.xml schema --> -<xsd:schema targetNamespace="http://java.sun.com/xml/ns/persistence" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - xmlns:persistence="http://java.sun.com/xml/ns/persistence" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.0"> - - <xsd:annotation> - <xsd:documentation> - @(#)persistence_1_0.xsd 1.0 Feb 9 2006 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER. - - Copyright 2005-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. - - The Eclipse Foundation elects to include this software in this - distribution under the CDDL license. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation><![CDATA[ - - This is the XML Schema for the persistence configuration file. - The file must be named "META-INF/persistence.xml" in the - persistence archive. - Persistence configuration files must indicate - the persistence schema by using the persistence namespace: - - http://java.sun.com/xml/ns/persistence - - and indicate the version of the schema by - using the version element as shown below: - - <persistence xmlns="http://java.sun.com/xml/ns/persistence" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://java.sun.com/xml/ns/persistence - http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" - version="1.0"> - ... - </persistence> - - ]]></xsd:documentation> - </xsd:annotation> - - <xsd:simpleType name="versionType"> - <xsd:restriction base="xsd:token"> - <xsd:pattern value="[0-9]+(\.[0-9]+)*"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:element name="persistence"> - <xsd:complexType> - <xsd:sequence> - - <!-- **************************************************** --> - - <xsd:element name="persistence-unit" - minOccurs="0" maxOccurs="unbounded"> - <xsd:complexType> - <xsd:annotation> - <xsd:documentation> - - Configuration of a persistence unit. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - - <!-- **************************************************** --> - - <xsd:element name="description" type="xsd:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Textual description of this persistence unit. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="provider" type="xsd:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Provider class that supplies EntityManagers for this - persistence unit. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="jta-data-source" type="xsd:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The container-specific name of the JTA datasource to use. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="non-jta-data-source" type="xsd:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The container-specific name of a non-JTA datasource to use. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="mapping-file" type="xsd:string" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - File containing mapping information. Loaded as a resource - by the persistence provider. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="jar-file" type="xsd:string" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Jar file that should be scanned for entities. - Not applicable to Java SE persistence units. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="class" type="xsd:string" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Class to scan for annotations. It should be annotated - with either @Entity, @Embeddable or @MappedSuperclass. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="exclude-unlisted-classes" type="xsd:boolean" - default="false" minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - When set to true then only listed classes and jars will - be scanned for persistent classes, otherwise the enclosing - jar or directory will also be scanned. Not applicable to - Java SE persistence units. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:element name="properties" minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - A list of vendor-specific properties. - - </xsd:documentation> - </xsd:annotation> - <xsd:complexType> - <xsd:sequence> - <xsd:element name="property" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - A name-value pair. - </xsd:documentation> - </xsd:annotation> - <xsd:complexType> - <xsd:attribute name="name" type="xsd:string" - use="required"/> - <xsd:attribute name="value" type="xsd:string" - use="required"/> - </xsd:complexType> - </xsd:element> - </xsd:sequence> - </xsd:complexType> - </xsd:element> - - </xsd:sequence> - - <!-- **************************************************** --> - - <xsd:attribute name="name" type="xsd:string" use="required"> - <xsd:annotation> - <xsd:documentation> - - Name used in code to reference this persistence unit. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - - <!-- **************************************************** --> - - <xsd:attribute name="transaction-type" - type="persistence:persistence-unit-transaction-type"> - <xsd:annotation> - <xsd:documentation> - - Type of transactions used by EntityManagers from this - persistence unit. - - </xsd:documentation> - </xsd:annotation> - </xsd:attribute> - - </xsd:complexType> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="version" type="persistence:versionType" - fixed="1.0" use="required"/> - </xsd:complexType> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:simpleType name="persistence-unit-transaction-type"> - <xsd:annotation> - <xsd:documentation> - - public enum TransactionType { JTA, RESOURCE_LOCAL }; - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="JTA"/> - <xsd:enumeration value="RESOURCE_LOCAL"/> - </xsd:restriction> - </xsd:simpleType> - -</xsd:schema> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_2.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_2.dtd deleted file mode 100644 index 5f439f42cd..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_2.dtd +++ /dev/null @@ -1,639 +0,0 @@ -<!-- -Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - - - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ -Copyright 1999 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - -<!-- -The web-app element is the root of the deployment descriptor for -a web application ---> - -<!ELEMENT web-app (icon?, display-name?, description?, distributable?, -context-param*, servlet*, servlet-mapping*, session-config?, -mime-mapping*, welcome-file-list?, error-page*, taglib*, -resource-ref*, security-constraint*, login-config?, security-role*, -env-entry*, ejb-ref*)> - -<!-- -The icon element contains a small-icon and a large-icon element -which specify the location within the web application for a small and -large image used to represent the web application in a GUI tool. At a -minimum, tools must accept GIF and JPEG format images. ---> - -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -The small-icon element contains the location within the web -application of a file containing a small (16x16 pixel) icon image. ---> - -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The large-icon element contains the location within the web -application of a file containing a large (32x32 pixel) icon image. ---> - -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended -to be displayed by GUI tools ---> - -<!ELEMENT display-name (#PCDATA)> - -<!-- -The description element is used to provide descriptive text about -the parent element. ---> - -<!ELEMENT description (#PCDATA)> - -<!-- -The distributable element, by its presence in a web application -deployment descriptor, indicates that this web application is -programmed appropriately to be deployed into a distributed servlet -container ---> - -<!ELEMENT distributable EMPTY> - -<!-- -The context-param element contains the declaration of a web -application's servlet context initialization parameters. ---> - -<!ELEMENT context-param (param-name, param-value, description?)> - -<!-- -The param-name element contains the name of a parameter. ---> - -<!ELEMENT param-name (#PCDATA)> - -<!-- -The param-value element contains the value of a parameter. ---> - -<!ELEMENT param-value (#PCDATA)> - -<!-- -The servlet element 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. ---> - -<!ELEMENT servlet (icon?, servlet-name, display-name?, description?, -(servlet-class|jsp-file), init-param*, load-on-startup?, security-role-ref*)> - -<!-- -The servlet-name element contains the canonical name of the -servlet. ---> - -<!ELEMENT servlet-name (#PCDATA)> - -<!-- -The servlet-class element contains the fully qualified class name -of the servlet. ---> - -<!ELEMENT servlet-class (#PCDATA)> - -<!-- -The jsp-file element contains the full path to a JSP file within -the web application. ---> - -<!ELEMENT jsp-file (#PCDATA)> - -<!-- -The init-param element contains a name/value pair as an -initialization param of the servlet ---> - -<!ELEMENT init-param (param-name, param-value, description?)> - -<!-- -The load-on-startup element indicates that this servlet should be -loaded on the startup of the web application. The optional contents of -these element must be a positive integer indicating the order in which -the servlet should be loaded. Lower integers are loaded before higher -integers. If no value is specified, or if the value specified is not a -positive integer, the container is free to load it at any time in the -startup sequence. ---> - -<!ELEMENT load-on-startup (#PCDATA)> - -<!-- -The servlet-mapping element defines a mapping between a servlet -and a url pattern ---> - -<!ELEMENT servlet-mapping (servlet-name, url-pattern)> - -<!-- -The url-pattern element contains the url pattern of the -mapping. Must follow the rules specified in Section 10 of the Servlet -API Specification. ---> - -<!ELEMENT url-pattern (#PCDATA)> - -<!-- -The session-config element defines the session parameters for -this web application. ---> - -<!ELEMENT session-config (session-timeout?)> - -<!-- -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. ---> - -<!ELEMENT session-timeout (#PCDATA)> - -<!-- -The mime-mapping element defines a mapping between an extension -and a mime type. ---> - -<!ELEMENT mime-mapping (extension, mime-type)> - -<!-- -The extension element contains a string describing an -extension. example: "txt" ---> - -<!ELEMENT extension (#PCDATA)> - -<!-- -The mime-type element contains a defined mime type. example: -"text/plain" ---> - -<!ELEMENT mime-type (#PCDATA)> - -<!-- -The welcome-file-list contains an ordered list of welcome files -elements. ---> - -<!ELEMENT welcome-file-list (welcome-file+)> - -<!-- -The welcome-file element contains file name to use as a default -welcome file, such as index.html ---> - -<!ELEMENT welcome-file (#PCDATA)> - -<!-- -The taglib element is used to describe a JSP tag library. ---> - -<!ELEMENT taglib (taglib-uri, taglib-location)> - -<!-- -The taglib-uri element describes a URI, relative to the location -of the web.xml document, identifying a Tag Library used in the Web -Application. ---> - -<!ELEMENT taglib-uri (#PCDATA)> - -<!-- -the taglib-location element contains the location (as a resource -relative to the root of the web application) where to find the Tag -Libary Description file for the tag library. ---> - -<!ELEMENT taglib-location (#PCDATA)> - -<!-- -The error-page element contains a mapping between an error code -or exception type to the path of a resource in the web application ---> - -<!ELEMENT error-page ((error-code | exception-type), location)> - -<!-- -The error-code contains an HTTP error code, ex: 404 ---> - -<!ELEMENT error-code (#PCDATA)> - -<!-- -The exception type contains a fully qualified class name of a -Java exception type. ---> - -<!ELEMENT exception-type (#PCDATA)> - -<!-- -The location element contains the location of the resource in the -web application ---> - -<!ELEMENT location (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of a Web -Application's reference to an external resource. ---> - -<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth)> - -<!-- -The res-ref-name element specifies the name of the resource -factory reference name. ---> - -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-type element specifies the (Java class) type of the data -source. ---> - -<!ELEMENT res-type (#PCDATA)> - -<!-- -The res-auth element indicates whether the application component -code performs resource signon programmatically or whether the -container signs onto the resource based on the principle mapping -information supplied by the deployer. Must be CONTAINER or SERVLET ---> - -<!ELEMENT res-auth (#PCDATA)> - -<!-- -The security-constraint element is used to associate security -constraints with one or more web resource collections ---> - -<!ELEMENT security-constraint (web-resource-collection+, -auth-constraint?, user-data-constraint?)> - -<!-- -The web-resource-collection element 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. ---> - -<!ELEMENT web-resource-collection (web-resource-name, description?, -url-pattern*, http-method*)> - -<!-- -The web-resource-name contains the name of this web resource -collection ---> - -<!ELEMENT web-resource-name (#PCDATA)> - -<!-- -The http-method contains an HTTP method (GET | POST |...) ---> - -<!ELEMENT http-method (#PCDATA)> - -<!-- -The user-data-constraint element is used to indicate how data -communicated between the client and container should be protected ---> - -<!ELEMENT user-data-constraint (description?, transport-guarantee)> - -<!-- -The transport-guarantee element 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. ---> - -<!ELEMENT transport-guarantee (#PCDATA)> - -<!-- -The auth-constraint element indicates the user roles that should -be permitted access to this resource collection. The role used here -must appear in a security-role-ref element. ---> - -<!ELEMENT auth-constraint (description?, role-name*)> - -<!-- -The role-name element contains the name of a security role. ---> - -<!ELEMENT role-name (#PCDATA)> - -<!-- -The login-config element 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. ---> - -<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)> - -<!-- -The realm name element specifies the realm name to use in HTTP -Basic authorization ---> - -<!ELEMENT realm-name (#PCDATA)> - -<!-- -The form-login-config element 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. ---> - -<!ELEMENT form-login-config (form-login-page, form-error-page)> - -<!-- -The form-login-page element defines the location in the web app -where the page that can be used for login can be found ---> - -<!ELEMENT form-login-page (#PCDATA)> - -<!-- -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 ---> - -<!ELEMENT form-error-page (#PCDATA)> - -<!-- -The auth-method element 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 for this element are "BASIC", "DIGEST", -"FORM", or "CLIENT-CERT". ---> - -<!ELEMENT auth-method (#PCDATA)> - -<!-- -The security-role element contains the declaration of a security -role which is used in the security-constraints placed on the web -application. ---> - -<!ELEMENT security-role (description?, role-name)> - -<!-- -The role-name element contains the name of a role. This element -must contain a non-empty string. ---> - -<!ELEMENT security-role-ref (description?, role-name, role-link)> - -<!-- -The role-link element is used to link a security role 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. ---> - -<!ELEMENT role-link (#PCDATA)> - -<!-- -The env-entry element contains the declaration of an -application's environment entry. This element is required to be -honored on in J2EE compliant servlet containers. ---> - -<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?, -env-entry-type)> - -<!-- -The env-entry-name contains the name of an application's -environment entry ---> - -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-value element contains the value of an -application's environment entry ---> - -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The env-entry-type element contains the fully qualified Java type -of the environment entry value that is expected by the application -code. The following are the legal values of env-entry-type: -java.lang.Boolean, java.lang.String, java.lang.Integer, -java.lang.Double, java.lang.Float. ---> - -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The ejb-ref element is used to declare a reference to an -enterprise bean. ---> - -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, remote, -ejb-link?)> - -<!-- -The ejb-ref-name element contains the name of an EJB -reference. This is the JNDI name that the servlet code uses to get a -reference to the enterprise bean. ---> - -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected java class type of -the referenced EJB. ---> - -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- -The ejb-home element contains the fully qualified name of the -EJB's home interface ---> - -<!ELEMENT home (#PCDATA)> - -<!-- -The ejb-remote element contains the fully qualified name of the -EJB's remote interface ---> - -<!ELEMENT remote (#PCDATA)> - -<!-- -The ejb-link element is used in the ejb-ref element to specify -that an EJB reference is linked to an EJB in an encompassing Java2 -Enterprise Edition (J2EE) application package. The value of the -ejb-link element must be the ejb-name of and EJB in the J2EE -application package. ---> - -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ID mechanism is to allow tools to easily make tool-specific -references to the elements of the deployment descriptor. This allows -tools that produce additional deployment information (i.e information -beyond the standard deployment descriptor information) to store the -non-standard information in a separate file, and easily refer from -these tools-specific files to the information in the standard web-app -deployment descriptor. ---> - -<!ATTLIST web-app id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST distributable id ID #IMPLIED> -<!ATTLIST context-param id ID #IMPLIED> -<!ATTLIST param-name id ID #IMPLIED> -<!ATTLIST param-value id ID #IMPLIED> -<!ATTLIST servlet id ID #IMPLIED> -<!ATTLIST servlet-name id ID #IMPLIED> -<!ATTLIST servlet-class id ID #IMPLIED> -<!ATTLIST jsp-file id ID #IMPLIED> -<!ATTLIST init-param id ID #IMPLIED> -<!ATTLIST load-on-startup id ID #IMPLIED> -<!ATTLIST servlet-mapping id ID #IMPLIED> -<!ATTLIST url-pattern id ID #IMPLIED> -<!ATTLIST session-config id ID #IMPLIED> -<!ATTLIST session-timeout id ID #IMPLIED> -<!ATTLIST mime-mapping id ID #IMPLIED> -<!ATTLIST extension id ID #IMPLIED> -<!ATTLIST mime-type id ID #IMPLIED> -<!ATTLIST welcome-file-list id ID #IMPLIED> -<!ATTLIST welcome-file id ID #IMPLIED> -<!ATTLIST taglib id ID #IMPLIED> -<!ATTLIST taglib-uri id ID #IMPLIED> -<!ATTLIST taglib-location id ID #IMPLIED> -<!ATTLIST error-page id ID #IMPLIED> -<!ATTLIST error-code id ID #IMPLIED> -<!ATTLIST exception-type id ID #IMPLIED> -<!ATTLIST location id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST security-constraint id ID #IMPLIED> -<!ATTLIST web-resource-collection id ID #IMPLIED> -<!ATTLIST web-resource-name id ID #IMPLIED> -<!ATTLIST http-method id ID #IMPLIED> -<!ATTLIST user-data-constraint id ID #IMPLIED> -<!ATTLIST transport-guarantee id ID #IMPLIED> -<!ATTLIST auth-constraint id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST login-config id ID #IMPLIED> -<!ATTLIST realm-name id ID #IMPLIED> -<!ATTLIST form-login-config id ID #IMPLIED> -<!ATTLIST form-login-page id ID #IMPLIED> -<!ATTLIST form-error-page id ID #IMPLIED> -<!ATTLIST auth-method id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST security-role-ref id ID #IMPLIED> -<!ATTLIST role-link id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_3.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_3.dtd deleted file mode 100644 index 5e3ab01c0f..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_3.dtd +++ /dev/null @@ -1,1063 +0,0 @@ -<!-- -Copyright (c) 2000 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 embodied in the product that is 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 in other countries. - -This document and the product to which it pertains are distributed -under licenses restricting their use, copying, distribution, and -decompilation. This document may be reproduced and distributed but may -not be changed 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, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and and -Enterprise JavaBeans 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. - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED -WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR -NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH -DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. - - -_________________________________________________________________________ - -Copyright (c) 2000 Sun Microsystems, Inc., -901 San Antonio Road, -Palo Alto, California 94303, E'tats-Unis. -Tous droits re'serve's. - -Sun Microsystems, Inc. a les droits de proprie'te' intellectuels -relatants a` la technologie incorpore'e dans le produit qui est de'crit -dans ce document. En particulier, et sans la limitation, ces droits de -proprie'te' intellectuels peuvent inclure un ou plus des brevets -ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les -brevets plus supple'mentaires ou les applications de brevet en attente -dans les E'tats-Unis et dans les autres pays. - -Ce produit ou document est prote'ge' par un copyright et distribue' -avec des licences qui en restreignent l'utilisation, la copie, la -distribution, et la de'compilation. Ce documention associe n peut -e^tre reproduite et distribuer, par quelque moyen que ce soit, sans -l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de -licence, le cas e'che'ant. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright et -licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail et and -Enterprise JavaBeans sont des marques de fabrique ou des marques -de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres -pays. - -LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT -EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS -NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A -L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE -CONTREFAC,ON. ---> - -<!-- -This is the XML DTD for the Servlet 2.3 deployment descriptor. -All Servlet 2.3 deployment descriptors must include a DOCTYPE -of the following form: - - <!DOCTYPE web-app PUBLIC - "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" - "http://java.sun.com/dtd/web-app_2_3.dtd"> - ---> - -<!-- -The following conventions apply to all J2EE deployment descriptor -elements unless indicated otherwise. - -- In elements that contain PCDATA, leading and trailing whitespace - in the data may be ignored. - -- In elements whose value is an "enumerated type", the value is - case sensitive. - -- 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 web-app element is the root of the deployment descriptor for -a web application. ---> -<!ELEMENT web-app (icon?, display-name?, description?, distributable?, -context-param*, filter*, filter-mapping*, listener*, servlet*, -servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?, -error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*, -login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)> - -<!-- -The auth-constraint element 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. - - -Used in: security-constraint ---> -<!ELEMENT auth-constraint (description?, role-name*)> - -<!-- -The auth-method element 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 for this element are "BASIC", "DIGEST", -"FORM", or "CLIENT-CERT". - -Used in: login-config ---> -<!ELEMENT auth-method (#PCDATA)> - -<!-- -The context-param element contains the declaration of a web -application's servlet context initialization parameters. - -Used in: web-app ---> -<!ELEMENT context-param (param-name, param-value, description?)> - -<!-- -The description element is used to provide text describing the parent -element. The description element should include any information that -the web application war file producer wants to provide to the consumer of -the web application war file (i.e., to the Deployer). Typically, the tools -used by the web application war file consumer will display the description -when processing the parent element that contains the description. - -Used in: auth-constraint, context-param, ejb-local-ref, ejb-ref, -env-entry, filter, init-param, resource-env-ref, resource-ref, run-as, -security-role, security-role-ref, servlet, user-data-constraint, -web-app, web-resource-collection ---> -<!ELEMENT description (#PCDATA)> - -<!-- -The display-name element contains a short name that is intended to be -displayed by tools. The display name need not be unique. - -Used in: filter, security-constraint, servlet, web-app - -Example: - -<display-name>Employee Self Service</display-name> ---> -<!ELEMENT display-name (#PCDATA)> - -<!-- -The distributable element, by its presence in a web application -deployment descriptor, indicates that this web application is -programmed appropriately to be deployed into a distributed servlet -container - -Used in: web-app ---> -<!ELEMENT distributable EMPTY> - -<!-- -The ejb-link element is used in the ejb-ref or ejb-local-ref -elements to specify that an EJB reference is linked to an -enterprise bean. - -The name in the ejb-link element is 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 war file -containing the web application that is referencing the enterprise bean. -This allows multiple enterprise beans with the same ejb-name to be -uniquely identified. - -Used in: ejb-local-ref, ejb-ref - -Examples: - - <ejb-link>EmployeeRecord</ejb-link> - - <ejb-link>../products/product.jar#ProductEJB</ejb-link> - ---> -<!ELEMENT ejb-link (#PCDATA)> - -<!-- -The ejb-local-ref element is used for the declaration of a reference to -an enterprise bean's local home. The declaration consists of: - - - an optional description - - the EJB reference name used in the code of the web application - that's referencing the enterprise bean - - the expected type of the referenced enterprise bean - - the expected local home and local interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the referenced - enterprise bean - -Used in: web-app ---> -<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type, - local-home, local, ejb-link?)> - -<!-- -The ejb-ref element is used for the declaration of a reference to -an enterprise bean's home. The declaration consists of: - - - an optional description - - the EJB reference name used in the code of - the web application that's referencing the enterprise bean - - the expected type of the referenced enterprise bean - - the expected home and remote interfaces of the referenced - enterprise bean - - optional ejb-link information, used to specify the referenced - enterprise bean - -Used in: web-app ---> -<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, - home, remote, ejb-link?)> - -<!-- -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/". - -Used in: ejb-local-ref, ejb-ref - -Example: - -<ejb-ref-name>ejb/Payroll</ejb-ref-name> ---> -<!ELEMENT ejb-ref-name (#PCDATA)> - -<!-- -The ejb-ref-type element contains the expected type of the -referenced enterprise bean. - -The ejb-ref-type element must be one of the following: - - <ejb-ref-type>Entity</ejb-ref-type> - <ejb-ref-type>Session</ejb-ref-type> - -Used in: ejb-local-ref, ejb-ref ---> -<!ELEMENT ejb-ref-type (#PCDATA)> - -<!-- -The env-entry element contains the declaration of a web application's -environment entry. The declaration consists of an optional -description, the name of the environment entry, and an optional -value. If a value is not specified, one must be supplied -during deployment. ---> -<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?, -env-entry-type)> - -<!-- -The env-entry-name element contains the name of a web applications'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. - -Example: - -<env-entry-name>minAmount</env-entry-name> - -Used in: env-entry ---> -<!ELEMENT env-entry-name (#PCDATA)> - -<!-- -The env-entry-type element contains the fully-qualified Java type of -the environment entry value that is expected by the web application's -code. - -The following are the legal values of env-entry-type: - - 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 - -Used in: env-entry ---> -<!ELEMENT env-entry-type (#PCDATA)> - -<!-- -The env-entry-value element contains the value of a web application'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> - -Used in: env-entry ---> -<!ELEMENT env-entry-value (#PCDATA)> - -<!-- -The error-code contains an HTTP error code, ex: 404 - -Used in: error-page ---> -<!ELEMENT error-code (#PCDATA)> - -<!-- -The error-page element contains a mapping between an error code -or exception type to the path of a resource in the web application - -Used in: web-app ---> -<!ELEMENT error-page ((error-code | exception-type), location)> - -<!-- -The exception type contains a fully qualified class name of a -Java exception type. - -Used in: error-page ---> -<!ELEMENT exception-type (#PCDATA)> - -<!-- -The extension element contains a string describing an -extension. example: "txt" - -Used in: mime-mapping ---> -<!ELEMENT extension (#PCDATA)> - -<!-- -Declares 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 ---> -<!ELEMENT filter (icon?, filter-name, display-name?, description?, -filter-class, init-param*)> - -<!-- -The fully qualified classname of the filter. - -Used in: filter ---> -<!ELEMENT filter-class (#PCDATA)> - -<!-- -Declaration of the filter mappings in this web application. 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. - -Used in: web-app ---> -<!ELEMENT filter-mapping (filter-name, (url-pattern | servlet-name))> - -<!-- -The logical name of the filter. This name is used to map the filter. -Each filter name is unique within the web application. - -Used in: filter, filter-mapping ---> -<!ELEMENT filter-name (#PCDATA)> - -<!-- -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. - -Used in: form-login-config ---> -<!ELEMENT form-error-page (#PCDATA)> - -<!-- -The form-login-config element 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 ---> -<!ELEMENT form-login-config (form-login-page, form-error-page)> - -<!-- -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. - -Used in: form-login-config ---> -<!ELEMENT form-login-page (#PCDATA)> - -<!-- -The home element contains the fully-qualified name of the enterprise -bean's home interface. - -Used in: ejb-ref - -Example: - -<home>com.aardvark.payroll.PayrollHome</home> ---> -<!ELEMENT home (#PCDATA)> - -<!-- -The http-method contains an HTTP method (GET | POST |...). - -Used in: web-resource-collection ---> -<!ELEMENT http-method (#PCDATA)> - -<!-- -The icon element contains small-icon and large-icon elements that -specify the file names for small and a large GIF or JPEG icon images -used to represent the parent element in a GUI tool. - -Used in: filter, servlet, web-app ---> -<!ELEMENT icon (small-icon?, large-icon?)> - -<!-- -The init-param element contains a name/value pair as an -initialization param of the servlet - -Used in: filter, servlet ---> -<!ELEMENT init-param (param-name, param-value, description?)> - -<!-- -The jsp-file element contains the full path to a JSP file within -the web application beginning with a `/'. - -Used in: servlet ---> -<!ELEMENT jsp-file (#PCDATA)> - -<!-- -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 web application's -war file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<large-icon>employee-service-icon32x32.jpg</large-icon> ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- -The listener element indicates the deployment properties for a web -application listener bean. - -Used in: web-app ---> -<!ELEMENT listener (listener-class)> - -<!-- -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. - - -Used in: listener ---> -<!ELEMENT listener-class (#PCDATA)> - -<!-- -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. - -Used in: servlet ---> -<!ELEMENT load-on-startup (#PCDATA)> - -<!-- - -The local element contains the fully-qualified name of the -enterprise bean's local interface. - -Used in: ejb-local-ref - ---> -<!ELEMENT local (#PCDATA)> - -<!-- - -The local-home element contains the fully-qualified name of the -enterprise bean's local home interface. - -Used in: ejb-local-ref ---> -<!ELEMENT local-home (#PCDATA)> - -<!-- -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 `/'. - -Used in: error-page ---> -<!ELEMENT location (#PCDATA)> - -<!-- -The login-config element 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 ---> -<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)> - -<!-- -The mime-mapping element defines a mapping between an extension -and a mime type. - -Used in: web-app ---> -<!ELEMENT mime-mapping (extension, mime-type)> - -<!-- -The mime-type element contains a defined mime type. example: -"text/plain" - -Used in: mime-mapping ---> -<!ELEMENT mime-type (#PCDATA)> - -<!-- -The param-name element contains the name of a parameter. Each parameter -name must be unique in the web application. - - -Used in: context-param, init-param ---> -<!ELEMENT param-name (#PCDATA)> - -<!-- -The param-value element contains the value of a parameter. - -Used in: context-param, init-param ---> -<!ELEMENT param-value (#PCDATA)> - -<!-- -The realm name element specifies the realm name to use in HTTP -Basic authorization. - -Used in: login-config ---> -<!ELEMENT realm-name (#PCDATA)> - -<!-- -The remote element contains the fully-qualified name of the enterprise -bean's remote interface. - -Used in: ejb-ref - -Example: - -<remote>com.wombat.empl.EmployeeService</remote> ---> -<!ELEMENT remote (#PCDATA)> - -<!-- -The res-auth element specifies whether the web application code signs -on programmatically to the resource manager, or whether the Container -will sign on to the resource manager on behalf of the web application. In the -latter case, the Container uses information that is supplied by the -Deployer. - -The value of this element must be one of the two following: - - <res-auth>Application</res-auth> - <res-auth>Container</res-auth> - -Used in: resource-ref ---> -<!ELEMENT res-auth (#PCDATA)> - -<!-- -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. - -Used in: resource-ref ---> -<!ELEMENT res-ref-name (#PCDATA)> - -<!-- -The res-sharing-scope element specifies whether connections obtained -through the given resource manager connection factory reference can be -shared. The value of this element, if specified, must be one of the -two following: - - <res-sharing-scope>Shareable</res-sharing-scope> - <res-sharing-scope>Unshareable</res-sharing-scope> - -The default value is Shareable. - -Used in: resource-ref ---> -<!ELEMENT res-sharing-scope (#PCDATA)> - -<!-- -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. - -Used in: resource-ref ---> -<!ELEMENT res-type (#PCDATA)> - -<!-- -The resource-env-ref element contains a declaration of a web application's -reference to an administered object associated with a resource -in the web application's environment. It consists of an optional -description, the resource environment reference name, and an -indication of the resource environment reference type expected by -the web application code. - -Used in: web-app - -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> ---> -<!ELEMENT resource-env-ref (description?, resource-env-ref-name, - resource-env-ref-type)> - -<!-- -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. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-name (#PCDATA)> - -<!-- -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. - -Used in: resource-env-ref ---> -<!ELEMENT resource-env-ref-type (#PCDATA)> - -<!-- -The resource-ref element contains a declaration of a web application's -reference to an external resource. It consists of an optional -description, the resource manager connection factory reference name, -the indication of the resource manager connection factory type -expected by the web application code, the type of authentication -(Application or Container), and an optional specification of the -shareability of connections obtained from the resource (Shareable or -Unshareable). - -Used in: web-app - -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> ---> -<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth, - res-sharing-scope?)> - -<!-- -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. - -Used in: security-role-ref ---> -<!ELEMENT role-link (#PCDATA)> - -<!-- -The role-name element contains the name of a security role. - -The name must conform to the lexical rules for an NMTOKEN. - -Used in: auth-constraint, run-as, security-role, security-role-ref ---> -<!ELEMENT role-name (#PCDATA)> - -<!-- -The run-as element specifies the run-as identity to be used for the -execution of the web application. It contains an optional description, and -the name of a security role. - -Used in: servlet ---> -<!ELEMENT run-as (description?, role-name)> - -<!-- -The security-constraint element is used to associate security -constraints with one or more web resource collections - -Used in: web-app ---> -<!ELEMENT security-constraint (display-name?, web-resource-collection+, -auth-constraint?, user-data-constraint?)> - -<!-- -The security-role element contains the definition of a security -role. The definition consists of an optional description of the -security role, and the security role name. - -Used in: web-app - -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> ---> -<!ELEMENT security-role (description?, role-name)> - -<!-- -The security-role-ref element contains the declaration of a security -role reference in the web application'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. - -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. - -Used in: servlet - ---> -<!ELEMENT security-role-ref (description?, role-name, role-link?)> - -<!-- -The servlet element 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 ---> -<!ELEMENT servlet (icon?, servlet-name, display-name?, description?, -(servlet-class|jsp-file), init-param*, load-on-startup?, run-as?, security-role-ref*)> - -<!-- -The servlet-class element contains the fully qualified class name -of the servlet. - -Used in: servlet ---> -<!ELEMENT servlet-class (#PCDATA)> - -<!-- -The servlet-mapping element defines a mapping between a servlet -and a url pattern - -Used in: web-app ---> -<!ELEMENT servlet-mapping (servlet-name, url-pattern)> - -<!-- -The servlet-name element contains the canonical name of the -servlet. Each servlet name is unique within the web application. - -Used in: filter-mapping, servlet, servlet-mapping ---> -<!ELEMENT servlet-name (#PCDATA)> - -<!-- -The session-config element defines the session parameters for -this web application. - -Used in: web-app ---> -<!ELEMENT session-config (session-timeout?)> - -<!-- -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. - -Used in: session-config ---> -<!ELEMENT session-timeout (#PCDATA)> - -<!-- -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 web application's -war file. - -The image may be either in the JPEG or GIF format. -The icon can be used by tools. - -Used in: icon - -Example: - -<small-icon>employee-service-icon16x16.jpg</small-icon> ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- -The taglib element is used to describe a JSP tag library. - -Used in: web-app ---> -<!ELEMENT taglib (taglib-uri, taglib-location)> - -<!-- -the taglib-location element contains the location (as a resource -relative to the root of the web application) where to find the Tag -Libary Description file for the tag library. - -Used in: taglib ---> -<!ELEMENT taglib-location (#PCDATA)> - -<!-- -The taglib-uri element describes a URI, relative to the location -of the web.xml document, identifying a Tag Library used in the Web -Application. - -Used in: taglib ---> -<!ELEMENT taglib-uri (#PCDATA)> - -<!-- -The transport-guarantee element 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 ---> -<!ELEMENT transport-guarantee (#PCDATA)> - -<!-- -The url-pattern element contains the url pattern of the mapping. Must -follow the rules specified in Section 11.2 of the Servlet API -Specification. - -Used in: filter-mapping, servlet-mapping, web-resource-collection ---> -<!ELEMENT url-pattern (#PCDATA)> - -<!-- -The user-data-constraint element is used to indicate how data -communicated between the client and container should be protected. - -Used in: security-constraint ---> -<!ELEMENT user-data-constraint (description?, transport-guarantee)> - -<!-- -The web-resource-collection element 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 ---> -<!ELEMENT web-resource-collection (web-resource-name, description?, -url-pattern*, http-method*)> - -<!-- -The web-resource-name contains the name of this web resource -collection. - -Used in: web-resource-collection ---> -<!ELEMENT web-resource-name (#PCDATA)> - -<!-- -The welcome-file element contains file name to use as a default -welcome file, such as index.html - -Used in: welcome-file-list ---> -<!ELEMENT welcome-file (#PCDATA)> - -<!-- -The welcome-file-list contains an ordered list of welcome files -elements. - -Used in: web-app ---> -<!ELEMENT welcome-file-list (welcome-file+)> - -<!-- -The ID mechanism is to allow tools that produce additional deployment -information (i.e., information beyond the standard deployment -descriptor information) to store the non-standard information in a -separate file, and easily refer from these tool-specific files to the -information in the standard deployment descriptor. - -Tools are not allowed to add the non-standard information into the -standard deployment descriptor. ---> - -<!ATTLIST auth-constraint id ID #IMPLIED> -<!ATTLIST auth-method id ID #IMPLIED> -<!ATTLIST context-param id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST distributable id ID #IMPLIED> -<!ATTLIST ejb-link id ID #IMPLIED> -<!ATTLIST ejb-local-ref id ID #IMPLIED> -<!ATTLIST ejb-ref id ID #IMPLIED> -<!ATTLIST ejb-ref-name id ID #IMPLIED> -<!ATTLIST ejb-ref-type id ID #IMPLIED> -<!ATTLIST env-entry id ID #IMPLIED> -<!ATTLIST env-entry-name id ID #IMPLIED> -<!ATTLIST env-entry-type id ID #IMPLIED> -<!ATTLIST env-entry-value id ID #IMPLIED> -<!ATTLIST error-code id ID #IMPLIED> -<!ATTLIST error-page id ID #IMPLIED> -<!ATTLIST exception-type id ID #IMPLIED> -<!ATTLIST extension id ID #IMPLIED> -<!ATTLIST filter id ID #IMPLIED> -<!ATTLIST filter-class id ID #IMPLIED> -<!ATTLIST filter-mapping id ID #IMPLIED> -<!ATTLIST filter-name id ID #IMPLIED> -<!ATTLIST form-error-page id ID #IMPLIED> -<!ATTLIST form-login-config id ID #IMPLIED> -<!ATTLIST form-login-page id ID #IMPLIED> -<!ATTLIST home id ID #IMPLIED> -<!ATTLIST http-method id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST init-param id ID #IMPLIED> -<!ATTLIST jsp-file id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST listener id ID #IMPLIED> -<!ATTLIST listener-class id ID #IMPLIED> -<!ATTLIST load-on-startup id ID #IMPLIED> -<!ATTLIST local id ID #IMPLIED> -<!ATTLIST local-home id ID #IMPLIED> -<!ATTLIST location id ID #IMPLIED> -<!ATTLIST login-config id ID #IMPLIED> -<!ATTLIST mime-mapping id ID #IMPLIED> -<!ATTLIST mime-type id ID #IMPLIED> -<!ATTLIST param-name id ID #IMPLIED> -<!ATTLIST param-value id ID #IMPLIED> -<!ATTLIST realm-name id ID #IMPLIED> -<!ATTLIST remote id ID #IMPLIED> -<!ATTLIST res-auth id ID #IMPLIED> -<!ATTLIST res-ref-name id ID #IMPLIED> -<!ATTLIST res-sharing-scope id ID #IMPLIED> -<!ATTLIST res-type id ID #IMPLIED> -<!ATTLIST resource-env-ref id ID #IMPLIED> -<!ATTLIST resource-env-ref-name id ID #IMPLIED> -<!ATTLIST resource-env-ref-type id ID #IMPLIED> -<!ATTLIST resource-ref id ID #IMPLIED> -<!ATTLIST role-link id ID #IMPLIED> -<!ATTLIST role-name id ID #IMPLIED> -<!ATTLIST run-as id ID #IMPLIED> -<!ATTLIST security-constraint id ID #IMPLIED> -<!ATTLIST security-role id ID #IMPLIED> -<!ATTLIST security-role-ref id ID #IMPLIED> -<!ATTLIST servlet id ID #IMPLIED> -<!ATTLIST servlet-class id ID #IMPLIED> -<!ATTLIST servlet-mapping id ID #IMPLIED> -<!ATTLIST servlet-name id ID #IMPLIED> -<!ATTLIST session-config id ID #IMPLIED> -<!ATTLIST session-timeout id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST taglib id ID #IMPLIED> -<!ATTLIST taglib-location id ID #IMPLIED> -<!ATTLIST taglib-uri id ID #IMPLIED> -<!ATTLIST transport-guarantee id ID #IMPLIED> -<!ATTLIST url-pattern id ID #IMPLIED> -<!ATTLIST user-data-constraint id ID #IMPLIED> -<!ATTLIST web-app id ID #IMPLIED> -<!ATTLIST web-resource-collection id ID #IMPLIED> -<!ATTLIST web-resource-name id ID #IMPLIED> -<!ATTLIST welcome-file id ID #IMPLIED> -<!ATTLIST welcome-file-list id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_4.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_4.xsd deleted file mode 100644 index 79a25138e4..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_4.xsd +++ /dev/null @@ -1,1234 +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/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="2.4"> - <xsd:annotation> - <xsd:documentation> - @(#)web-app_2_4.xsds 1.60 03/08/26 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2004 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the Servlet 2.4 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 J2EE - namespace: - - http://java.sun.com/xml/ns/j2ee - - 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/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="..." - version="2.4"> - ... - </web-app> - - 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/web-app_2_4.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - <xsd:include schemaLocation="jsp_2_0.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="web-app" type="j2ee:web-appType"> - <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 concatinate the element contents. The multiple occurance - 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="j2ee:servlet"/> - <xsd:field xpath="j2ee: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="j2ee:filter"/> - <xsd:field xpath="j2ee: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="j2ee:ejb-local-ref"/> - <xsd:field xpath="j2ee: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="j2ee:ejb-ref"/> - <xsd:field xpath="j2ee: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="j2ee:resource-env-ref"/> - <xsd:field xpath="j2ee: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="j2ee:message-destination-ref"/> - <xsd:field xpath="j2ee: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="j2ee:resource-ref"/> - <xsd:field xpath="j2ee: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="j2ee:env-entry"/> - <xsd:field xpath="j2ee: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="j2ee:security-role"/> - <xsd:field xpath="j2ee:role-name"/> - </xsd:key> - - <xsd:keyref name="web-app-role-name-references" - refer="j2ee: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="j2ee:servlet/j2ee:security-role-ref"/> - <xsd:field xpath="j2ee:role-link"/> - </xsd:keyref> - </xsd:element> - - -<!-- **************************************************** --> - - <xsd:complexType name="auth-constraintType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="j2ee:role-nameType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="auth-methodType"> - <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:restriction base="j2ee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="dispatcherType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="FORWARD"/> - <xsd:enumeration value="INCLUDE"/> - <xsd:enumeration value="REQUEST"/> - <xsd:enumeration value="ERROR"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="encodingType"> - <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:complexType name="error-codeType"> - <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:restriction base="j2ee:xsdPositiveIntegerType"> - <xsd:pattern value="\d{3}"/> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="error-pageType"> - <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:element name="error-code" - type="j2ee:error-codeType"/> - - <xsd:element name="exception-type" - type="j2ee:fully-qualified-classType"> - <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:element name="location" - type="j2ee:war-pathType"> - <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:complexType name="filter-mappingType"> - <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:element name="filter-name" - type="j2ee:filter-nameType"/> - <xsd:choice> - <xsd:element name="url-pattern" - type="j2ee:url-patternType"/> - <xsd:element name="servlet-name" - type="j2ee:servlet-nameType"/> - </xsd:choice> - <xsd:element name="dispatcher" - type="j2ee:dispatcherType" - minOccurs="0" maxOccurs="4"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="filter-nameType"> - <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:extension base="j2ee:nonEmptyStringType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="filterType"> - <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:group ref="j2ee:descriptionGroup"/> - <xsd:element name="filter-name" - type="j2ee:filter-nameType"/> - <xsd:element name="filter-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The fully qualified classname of the filter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="init-param" - type="j2ee:param-valueType" - minOccurs="0" maxOccurs="unbounded"> - <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:complexType name="form-login-configType"> - <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:element name="form-login-page" - type="j2ee:war-pathType"> - <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:element name="form-error-page" - type="j2ee:war-pathType"> - <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:complexType name="http-methodType"> - <xsd:annotation> - - <xsd:documentation> - - The http-method contains an HTTP method recognized by the - web-app, for example GET, POST, ... - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="GET"/> - <xsd:enumeration value="POST"/> - <xsd:enumeration value="PUT"/> - <xsd:enumeration value="DELETE"/> - <xsd:enumeration value="HEAD"/> - <xsd:enumeration value="OPTIONS"/> - <xsd:enumeration value="TRACE"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="locale-encoding-mapping-listType"> - <xsd:annotation> - <xsd:documentation> - - The locale-encoding-mapping-list contains one or more - locale-encoding-mapping(s). - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="locale-encoding-mapping" - type="j2ee:locale-encoding-mappingType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="locale-encoding-mappingType"> - <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:element name="locale" - type="j2ee:localeType"/> - <xsd:element name="encoding" - type="j2ee:encodingType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="localeType"> - <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:complexType name="login-configType"> - <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:element name="auth-method" - type="j2ee:auth-methodType" - minOccurs="0"/> - <xsd:element name="realm-name" - type="j2ee:string" minOccurs="0"> - <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:element name="form-login-config" - type="j2ee:form-login-configType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="mime-mappingType"> - <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:element name="extension" - type="j2ee:string"/> - <xsd:element name="mime-type" - type="j2ee:mime-typeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="mime-typeType"> - <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:restriction base="j2ee:string"> - <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="nonEmptyStringType"> - <xsd:annotation> - <xsd:documentation> - This type defines a string which contains at least one - character. - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:minLength value="1"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-constraintType"> - <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:element name="display-name" - type="j2ee:display-nameType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="web-resource-collection" - type="j2ee:web-resource-collectionType" - maxOccurs="unbounded"/> - <xsd:element name="auth-constraint" - type="j2ee:auth-constraintType" - minOccurs="0"/> - <xsd:element name="user-data-constraint" - type="j2ee:user-data-constraintType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-mappingType"> - <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:element name="servlet-name" - type="j2ee:servlet-nameType"/> - <xsd:element name="url-pattern" - type="j2ee:url-patternType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-nameType"> - <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:extension base="j2ee:nonEmptyStringType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servletType"> - <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:group ref="j2ee:descriptionGroup"/> - <xsd:element name="servlet-name" - type="j2ee:servlet-nameType"/> - <xsd:choice> - <xsd:element name="servlet-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The servlet-class element contains the fully - qualified class name of the servlet. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="jsp-file" - type="j2ee:jsp-fileType"/> - - </xsd:choice> - - <xsd:element name="init-param" - type="j2ee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="load-on-startup" - type="j2ee:xsdIntegerType" - minOccurs="0"> - <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:element name="run-as" - type="j2ee:run-asType" - minOccurs="0"/> - <xsd:element name="security-role-ref" - type="j2ee:security-role-refType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-configType"> - <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:element name="session-timeout" - type="j2ee:xsdIntegerType" - minOccurs="0"> - <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:complexType name="transport-guaranteeType"> - <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:restriction base="j2ee:string"> - <xsd:enumeration value="NONE"/> - <xsd:enumeration value="INTEGRAL"/> - <xsd:enumeration value="CONFIDENTIAL"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="user-data-constraintType"> - <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:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="transport-guarantee" - type="j2ee:transport-guaranteeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="war-pathType"> - <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:restriction base="j2ee:string"> - <xsd:pattern value="/.*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="web-app-versionType"> - <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.4"/> - </xsd:restriction> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:complexType name="web-appType"> - - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="distributable" - type="j2ee:emptyType"/> - <xsd:element name="context-param" - type="j2ee:param-valueType"> - - <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:element name="filter" - type="j2ee:filterType"/> - <xsd:element name="filter-mapping" - type="j2ee:filter-mappingType"/> - <xsd:element name="listener" - type="j2ee:listenerType"/> - <xsd:element name="servlet" - type="j2ee:servletType"/> - <xsd:element name="servlet-mapping" - type="j2ee:servlet-mappingType"/> - <xsd:element name="session-config" - type="j2ee:session-configType"/> - <xsd:element name="mime-mapping" - type="j2ee:mime-mappingType"/> - <xsd:element name="welcome-file-list" - type="j2ee:welcome-file-listType"/> - <xsd:element name="error-page" - type="j2ee:error-pageType"/> - <xsd:element name="jsp-config" - type="j2ee:jsp-configType"/> - <xsd:element name="security-constraint" - type="j2ee:security-constraintType"/> - <xsd:element name="login-config" - type="j2ee:login-configType"/> - <xsd:element name="security-role" - type="j2ee:security-roleType"/> - <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/> - <xsd:element name="message-destination" - type="j2ee:message-destinationType"/> - <xsd:element name="locale-encoding-mapping-list" - type="j2ee:locale-encoding-mapping-listType"/> - </xsd:choice> - - <xsd:attribute name="version" - type="j2ee:web-app-versionType" - use="required"/> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="web-resource-collectionType"> - <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:element name="web-resource-name" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - The web-resource-name contains the name of this web - resource collection. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="url-pattern" - type="j2ee:url-patternType" - maxOccurs="unbounded"/> - <xsd:element name="http-method" - type="j2ee:http-methodType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="welcome-file-listType"> - <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 name="welcome-file" - type="xsd:string" - maxOccurs="unbounded"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_5.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_5.xsd deleted file mode 100644 index 8c0902e129..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-app_2_5.xsd +++ /dev/null @@ -1,1271 +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="2.5"> - <xsd:annotation> - <xsd:documentation> - @(#)web-app_2_5.xsds 1.62 05/08/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 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:include schemaLocation="javaee_5.xsd"/> - <xsd:include schemaLocation="jsp_2_1.xsd"/> - - -<!-- **************************************************** --> - - <xsd:element name="web-app" type="javaee:web-appType"> - <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:complexType name="auth-constraintType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="role-name" - type="javaee:role-nameType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="auth-methodType"> - <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:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="dispatcherType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="FORWARD"/> - <xsd:enumeration value="INCLUDE"/> - <xsd:enumeration value="REQUEST"/> - <xsd:enumeration value="ERROR"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="encodingType"> - <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:complexType name="error-codeType"> - <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:restriction base="javaee:xsdPositiveIntegerType"> - <xsd:pattern value="\d{3}"/> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="error-pageType"> - <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:element name="error-code" - type="javaee:error-codeType"/> - - <xsd:element name="exception-type" - type="javaee:fully-qualified-classType"> - <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:element name="location" - type="javaee:war-pathType"> - <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:complexType name="filter-mappingType"> - <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:element name="filter-name" - type="javaee:filter-nameType"/> - <xsd:choice minOccurs="1" maxOccurs="unbounded"> - <xsd:element name="url-pattern" - type="javaee:url-patternType"/> - <xsd:element name="servlet-name" - type="javaee:servlet-nameType"/> - </xsd:choice> - <xsd:element name="dispatcher" - type="javaee:dispatcherType" - minOccurs="0" maxOccurs="4"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="filter-nameType"> - <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:extension base="javaee:nonEmptyStringType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="filterType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="filter-name" - type="javaee:filter-nameType"/> - <xsd:element name="filter-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The fully qualified classname of the filter. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="init-param" - type="javaee:param-valueType" - minOccurs="0" maxOccurs="unbounded"> - <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:complexType name="form-login-configType"> - <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:element name="form-login-page" - type="javaee:war-pathType"> - <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:element name="form-error-page" - type="javaee:war-pathType"> - <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:simpleType name="http-methodType"> - <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 name="load-on-startupType"> - <xsd:union memberTypes="javaee:null-charType xsd:integer"/> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:complexType name="locale-encoding-mapping-listType"> - <xsd:annotation> - <xsd:documentation> - - The locale-encoding-mapping-list contains one or more - locale-encoding-mapping(s). - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="locale-encoding-mapping" - type="javaee:locale-encoding-mappingType" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="locale-encoding-mappingType"> - <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:element name="locale" - type="javaee:localeType"/> - <xsd:element name="encoding" - type="javaee:encodingType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="localeType"> - <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:complexType name="login-configType"> - <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:element name="auth-method" - type="javaee:auth-methodType" - minOccurs="0"/> - <xsd:element name="realm-name" - type="javaee:string" minOccurs="0"> - <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:element name="form-login-config" - type="javaee:form-login-configType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="mime-mappingType"> - <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:element name="extension" - type="javaee:string"/> - <xsd:element name="mime-type" - type="javaee:mime-typeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="mime-typeType"> - <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:restriction base="javaee:string"> - <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="nonEmptyStringType"> - <xsd:annotation> - <xsd:documentation> - This type defines a string which contains at least one - character. - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:minLength value="1"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="null-charType"> - <xsd:restriction base="xsd:string"> - <xsd:enumeration value=""/> - </xsd:restriction> - </xsd:simpleType> - -<!-- **************************************************** --> - - <xsd:complexType name="security-constraintType"> - <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:element name="display-name" - type="javaee:display-nameType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="web-resource-collection" - type="javaee:web-resource-collectionType" - maxOccurs="unbounded"/> - <xsd:element name="auth-constraint" - type="javaee:auth-constraintType" - minOccurs="0"/> - <xsd:element name="user-data-constraint" - type="javaee:user-data-constraintType" - minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-mappingType"> - <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:element name="servlet-name" - type="javaee:servlet-nameType"/> - <xsd:element name="url-pattern" - type="javaee:url-patternType" - minOccurs="1" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servlet-nameType"> - <xsd:annotation> - <xsd:documentation> - - The servlet-name element contains the canonical name of the - servlet. Each servlet name is unique within the web - application. - The special servlet name of "*" may be used to reference all - servlets. - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:extension base="javaee:nonEmptyStringType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="servletType"> - <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:group ref="javaee:descriptionGroup"/> - <xsd:element name="servlet-name" - type="javaee:servlet-nameType"/> - <xsd:choice> - <xsd:element name="servlet-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The servlet-class element contains the fully - qualified class name of the servlet. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="jsp-file" - type="javaee:jsp-fileType"/> - - </xsd:choice> - - <xsd:element name="init-param" - type="javaee:param-valueType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="load-on-startup" - type="javaee:load-on-startupType" - minOccurs="0"> - <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:element name="run-as" - type="javaee:run-asType" - minOccurs="0"/> - <xsd:element name="security-role-ref" - type="javaee:security-role-refType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="session-configType"> - <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:element name="session-timeout" - type="javaee:xsdIntegerType" - minOccurs="0"> - <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:complexType name="transport-guaranteeType"> - <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:restriction base="javaee:string"> - <xsd:enumeration value="NONE"/> - <xsd:enumeration value="INTEGRAL"/> - <xsd:enumeration value="CONFIDENTIAL"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="user-data-constraintType"> - <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:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="transport-guarantee" - type="javaee:transport-guaranteeType"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="war-pathType"> - <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:restriction base="javaee:string"> - <xsd:pattern value="/.*"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:simpleType name="web-app-versionType"> - <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:complexType name="web-appType"> - - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="distributable" - type="javaee:emptyType"/> - <xsd:element name="context-param" - type="javaee:param-valueType"> - - <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:element name="filter" - type="javaee:filterType"/> - <xsd:element name="filter-mapping" - type="javaee:filter-mappingType"/> - <xsd:element name="listener" - type="javaee:listenerType"/> - <xsd:element name="servlet" - type="javaee:servletType"/> - <xsd:element name="servlet-mapping" - type="javaee:servlet-mappingType"/> - <xsd:element name="session-config" - type="javaee:session-configType"/> - <xsd:element name="mime-mapping" - type="javaee:mime-mappingType"/> - <xsd:element name="welcome-file-list" - type="javaee:welcome-file-listType"/> - <xsd:element name="error-page" - type="javaee:error-pageType"/> - <xsd:element name="jsp-config" - type="javaee:jsp-configType"/> - <xsd:element name="security-constraint" - type="javaee:security-constraintType"/> - <xsd:element name="login-config" - type="javaee:login-configType"/> - <xsd:element name="security-role" - type="javaee:security-roleType"/> - <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> - <xsd:element name="message-destination" - type="javaee:message-destinationType"/> - <xsd:element name="locale-encoding-mapping-list" - type="javaee:locale-encoding-mapping-listType"/> - </xsd:choice> - - <xsd:attribute name="version" - type="javaee:web-app-versionType" - use="required"/> - <xsd:attribute name="id" type="xsd:ID"/> - - <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:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="web-resource-collectionType"> - <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:element name="web-resource-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The web-resource-name contains the name of this web - resource collection. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="url-pattern" - type="javaee:url-patternType" - maxOccurs="unbounded"/> - <xsd:element name="http-method" - type="javaee:http-methodType" - minOccurs="0" maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="welcome-file-listType"> - <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 name="welcome-file" - type="xsd:string" - maxOccurs="unbounded"> - <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> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_0.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_0.dtd deleted file mode 100644 index 3e1c998e6c..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_0.dtd +++ /dev/null @@ -1,874 +0,0 @@ -<!-- - DTD for the JavaServer Faces Application Configuration File (Version 1.0) - - To support validation of your configuration file(s), include the following - DOCTYPE element at the beginning (after the "xml" declaration): - - <!DOCTYPE faces-config PUBLIC - "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN" - "http://java.sun.com/dtd/web-facesconfig_1_0.dtd"> - - $Id: web-facesconfig_1_0.dtd,v 1.1 2007/05/25 21:12:49 david_williams Exp $ - ---> - - -<!-- ==================== Defined Types =================================== --> - - -<!-- - An "Action" is a String that represents a method binding - expression that points at a method with no arguments that returns a - String. It must be bracketed with "#{}", for example, - "#{cardemo.buyCar}". ---> -<!ENTITY % Action "CDATA"> - - -<!-- - A "ClassName" is the fully qualified name of a Java class that is - instantiated to provide the functionality of the enclosing element. ---> -<!ENTITY % ClassName "CDATA"> - - -<!-- - An "Identifier" is a string of characters that conforms to the variable - naming conventions of the Java programming language (JLS Section ?.?.?). ---> -<!ENTITY % Identifier "CDATA"> - - -<!-- - A "JavaType" is either the fully qualified name of a Java class that is - instantiated to provide the functionality of the enclosing element, or - the name of a Java primitive type (such as int or char). The class name - or primitive type may optionally be followed by "[]" to indicate that - the underlying data must be an array, rather than a scalar variable. ---> -<!ENTITY % JavaType "CDATA"> - - -<!-- - A "Language" is a lower case two-letter code for a language as defined - by ISL-639. ---> -<!ENTITY % Language "CDATA"> - - -<!-- - A "ResourcePath" is the relative or absolute path to a resource file - (such as a logo image). ---> -<!ENTITY % ResourcePath "CDATA"> - - -<!-- - A "Scope" is the well-known name of a scope in which managed beans may - optionally be defined to be created in. ---> -<!ENTITY % Scope "(request|session|application)"> - - - -<!-- - A "ScopeOrNone" element defines the legal values for the - <managed-bean-scope> element's body content, which includes - all of the scopes respresented by the "Scope" type, plus the - "none" value indicating that a created bean should not be - stored into any scope. ---> -<!ENTITY % ScopeOrNone "(request|session|application|none)"> - - -<!-- - A "ViewIdPattern" is a pattern for matching view identifiers in - order to determine whether a particular navigation rule should be - fired. It must contain one of the following values: - - - The exact match for a view identifier that is recognized - by the the ViewHandler implementation being used (such as - "/index.jsp" if you are using the default ViewHandler). - - - A proper prefix of a view identifier, plus a trailing "*" - character. This pattern indicates that all view identifiers that - match the portion of the pattern up to the asterisk will match the - surrounding rule. When more than one match exists, the match with - the longest pattern is selected. - - - An "*" character, which means that this pattern applies to all - view identifiers. ---> -<!ENTITY % ViewIdPattern "CDATA"> - - -<!-- ==================== Top Level Elements ============================== --> - - -<!-- - The "faces-config" element is the root of the configuration information - hierarchy, and contains nested elements for all of the other configuration - settings. ---> -<!ELEMENT faces-config ((application|factory|component|converter|managed-bean|navigation-rule|referenced-bean|render-kit|lifecycle|validator)*)> -<!ATTLIST faces-config - xmlns CDATA #FIXED "http://java.sun.com/JSF/Configuration"> - - - -<!-- ==================== Definition Elements ============================= --> - - -<!-- - The "application" element provides a mechanism to define the various - per-application-singleton implementation artifacts for a particular web - application that is utilizing JavaServer Faces. For nested elements - that are not specified, the JSF implementation must provide a suitable - default. ---> -<!ELEMENT application ((action-listener|default-render-kit-id|message-bundle|navigation-handler|view-handler|state-manager|property-resolver|variable-resolver|locale-config)*)> - - -<!-- - The "factory" element provides a mechanism to define the various - Factories that comprise parts of the implementation of JavaServer - Faces. For nested elements that are not specified, the JSF - implementation must provide a suitable default. ---> -<!ELEMENT factory ((application-factory|faces-context-factory|lifecycle-factory|render-kit-factory)*)> - - -<!-- - The "attribute" element represents a named, typed, value associated with - the parent UIComponent via the generic attributes mechanism. - - Attribute names must be unique within the scope of the parent (or related) - component. ---> -<!ELEMENT attribute (description*, display-name*, icon*, attribute-name, attribute-class, default-value?, suggested-value?, attribute-extension*)> - -<!-- - Extension element for attribute. May contain implementation - specific content. ---> -<!ELEMENT attribute-extension ANY> - - -<!-- - The "component" element represents a concrete UIComponent implementation - class that should be registered under the specified type identifier, - along with its associated properties and attributes. Component types must - be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that are recognized - by the implementation logic of this component. Nested "property" elements - identify JavaBeans properties of the component class that may be exposed - for manipulation via tools. ---> -<!ELEMENT component (description*, display-name*, icon*, component-type, component-class, attribute*, property*, component-extension*)> - -<!-- - Extension element for component. May contain implementation - specific content. ---> -<!ELEMENT component-extension ANY> - - - -<!-- - The "converter" element represents a concrete Converter implementation - class that should be registered under the specified converter identifier. - Converter identifiers must be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that may be - configured on the corresponding UIComponent in order to affect the - operation of the Converter. Nested "property" elements identify JavaBeans - properties of the Converter implementation class that may be configured - to affect the operation of the Converter. ---> -<!ELEMENT converter (description*, display-name*, icon*, (converter-id | converter-for-class), converter-class, attribute*, property*)> - - -<!-- - The "icon" element contains "small-icon" and "large-icon" elements that - specify the resoruce paths for small and large GIF or JPG icon images - used to represent the parent element in a GUI tool. ---> -<!ELEMENT icon (small-icon?, large-icon?)> -<!ATTLIST icon xml:lang %Language; #IMPLIED> - -<!-- - The "lifecycle" element provides a mechanism to specify - modifications to the behaviour of the default Lifecycle - implementation for this web application. ---> -<!ELEMENT lifecycle (phase-listener*)> - -<!-- - The "locale-config" element allows the app developer to declare the - supported locales for this application. ---> -<!ELEMENT locale-config (default-locale?, supported-locale*)> - -<!-- - The "managed-bean" element represents a JavaBean, of a particular class, - that will be dynamically instantiated at runtime (by the default - VariableResolver implementation) if it is referenced as the first element - of a value binding expression, and no corresponding bean can be - identified in any scope. In addition to the creation of the managed bean, - and the optional storing of it into the specified scope, the nested - managed-property elements can be used to initialize the contents of - settable JavaBeans properties of the created instance. ---> -<!ELEMENT managed-bean (description*, display-name*, icon*, managed-bean-name, managed-bean-class, managed-bean-scope, (managed-property* | map-entries | list-entries))> - - -<!-- - The "managed-property" element represents an individual property of a - managed bean that will be configured to the specified value (or value set) - if the corresponding managed bean is automatically created. ---> -<!ELEMENT managed-property (description*, display-name*, icon*, property-name, property-class?, (map-entries|null-value|value|list-entries))> - - -<!-- - The "map-entry" element reprsents a single key-entry pair that - will be added to the computed value of a managed property of type - java.util.Map. ---> -<!ELEMENT map-entry (key, (null-value|value))> - - -<!-- - The "map-entries' element represents a set of key-entry pairs that - will be added to the computed value of a managed property of type - java.util.Map. In addition, the Java class types of the key and entry - values may be optionally declared. ---> -<!ELEMENT map-entries (key-class?, value-class?, map-entry*)> - - -<!-- - The base name of a resource bundle representing the message resources - for this application. See the JavaDocs for the "java.util.ResourceBundle" - class for more information on the syntax of resource bundle names. ---> - -<!ELEMENT message-bundle (#PCDATA)> - - -<!-- - The "navigation-case" element describes a particular combination of - conditions that must match for this case to be executed, and the - view id of the component tree that should be selected next. ---> -<!ELEMENT navigation-case (description*, display-name*, icon*, from-action?, from-outcome?, to-view-id, redirect?)> - - -<!-- - The "navigation-rule" element represents an individual decision rule - that will be utilized by the default NavigationHandler - implementation to make decisions on what view should be displayed - next, based on the view id being processed. ---> -<!ELEMENT navigation-rule (description*, display-name*, icon*, from-view-id?, navigation-case*)> - - -<!-- - The "property" element represents a JavaBean property of the Java class - represented by our parent element. - - Property names must be unique within the scope of the Java class - that is represented by the parent element, and must correspond to - property names that will be recognized when performing introspection - against that class via java.beans.Introspector. ---> -<!ELEMENT property (description*, display-name*, icon*, property-name, property-class, default-value?, suggested-value?, property-extension*)> - -<!-- - Extension element for property. May contain implementation - specific content. ---> -<!ELEMENT property-extension ANY> - -<!-- - The "referenced-bean" element represents at design time the promise - that a Java object of the specified type will exist at runtime in some - scope, under the specified key. This can be used by design time tools - to construct user interface dialogs based on the properties of the - specified class. The presence or absence of a referenced bean - element has no impact on the JavaServer Faces runtime environment - inside a web application. ---> -<!ELEMENT referenced-bean (description*, display-name*, icon*, referenced-bean-name, referenced-bean-class)> - - -<!-- - The "render-kit" element represents a concrete RenderKit implementation - that should be registered under the specified render-kit-id. If no - render-kit-id is specified, the identifier of the default RenderKit - (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed. ---> -<!ELEMENT render-kit (description*, display-name*, icon*, render-kit-id?, render-kit-class?, renderer*)> - - -<!-- - The "renderer" element represents a concrete Renderer implementation - class that should be registered under the specified component family - and renderer type identifiers, in the RenderKit associated with the - parent "render-kit" element. Combinations of component family and renderer - type must be unique within the RenderKit associated with the parent - "render-kit" element. - - Nested "attribute" elements identify generic component attributes that - are recognized by this renderer. ---> -<!ELEMENT renderer (description*, display-name*, icon*, component-family, renderer-type, renderer-class, attribute*, renderer-extension*)> - -<!-- - Extension element for renderer. May contain implementation - specific content. ---> -<!ELEMENT renderer-extension ANY> - -<!-- - The "validator" element represents a concrete Validator implementation - class that should be registered under the specified validator identifier. - Validator identifiers must be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that may be - configured on the corresponding UIComponent in order to affect the - operation of the Validator. Nested "property" elements identify JavaBeans - properties of the Validator implementation class that may be configured - to affect the operation of the Validator. ---> -<!ELEMENT validator (description*, display-name*, icon*, validator-id, validator-class, attribute*, property*)> - - -<!-- - The "list-entries" element represents a set of initialization - elements for a managed property that is a java.util.List or an - array. In the former case, the "value-class" element can optionally - be used to declare the Java type to which each value should be - converted before adding it to the Collection. ---> -<!ELEMENT list-entries (value-class?, (null-value|value)*)> - - -<!-- ==================== Subordinate Elements ============================ --> - - -<!-- - The "action-listener" element contains the fully qualified class name - of the concrete ActionListener implementation class that will be called - during the Invoke Application phase of the request processing lifecycle. - It must be of type "ClassName". ---> -<!ELEMENT action-listener (#PCDATA)> - -<!-- - The "application-factory" element contains the fully qualified class - name of the concrete ApplicationFactory implementation class that - will be called when FactoryFinder.getFactory(APPLICATION_FACTORY) is - called. It must be of type "ClassName". ---> -<!ELEMENT application-factory (#PCDATA)> - -<!-- - The "attribute-class" element represents the Java type of the value - associated with this attribute name. It must be of type "ClassName". ---> -<!ELEMENT attribute-class (#PCDATA)> - - -<!-- - The "attribute-name" element represents the name under which the - corresponding value will be stored, in the generic attributes of the - UIComponent we are related to. ---> -<!ELEMENT attribute-name (#PCDATA)> - - -<!-- - The "component-class" element represents the fully qualified class name - of a concrete UIComponent implementation class. It must be of - type "ClassName". ---> -<!ELEMENT component-class (#PCDATA)> - - -<!-- - The "component-family" element represents the component family for - which the Renderer represented by the parent "renderer" element will be - used. ---> -<!ELEMENT component-family (#PCDATA)> - -<!-- - The "component-type" element represents the name under which the - corresponding UIComponent class should be registered. ---> -<!ELEMENT component-type (#PCDATA)> - - -<!-- - The "converter-class" element represents the fully qualified class name - of a concrete Converter implementation class. It must be of - type "ClassName". ---> -<!ELEMENT converter-class (#PCDATA)> - - -<!-- - The "converter-for-class" element represents the fully qualified class name - for which a Converter class will be registered. It must be of - type "ClassName". ---> -<!ELEMENT converter-for-class (#PCDATA)> - - -<!-- - The "converter-id" element represents the identifier under which the - corresponding Converter class should be registered. ---> -<!ELEMENT converter-id (#PCDATA)> - -<!-- - The "default-render-kit-id" element allows the application to define - a renderkit to be used other than the standard one. ---> -<!ELEMENT default-render-kit-id (#PCDATA)> - -<!-- - The "default-locale" element declares the default locale for this - application instance. It must be specified as - :language:[_:country:[_:variant:]] without the colons, for example - "ja_JP_SJIS". The separators between the segments may be '-' or - '_'. ---> -<!ELEMENT default-locale (#PCDATA)> - -<!-- - The "default-value" contains the value for the property or attribute - in which this element resides. This value differs from the - "suggested-value" in that the property or attribute must take the - value, whereas in "suggested-value" taking the value is optional. ---> -<!ELEMENT default-value (#PCDATA)> - -<!-- - The "description" element contains a textual description of the element - it is nested in, optionally flagged with a language code using the - "xml:lang" attribute. ---> -<!ELEMENT description ANY> -<!ATTLIST description xml:lang %Language; #IMPLIED> - - -<!-- - The "display-name" element is a short descriptive name describing the - entity associated with the element it is nested in, intended to be - displayed by tools, and optionally flagged with a language code using - the "xml:lang" attribute. ---> -<!ELEMENT display-name (#PCDATA)> -<!ATTLIST display-name xml:lang %Language; #IMPLIED> - -<!-- - The "faces-context-factory" element contains the fully qualified - class name of the concrete FacesContextFactory implementation class - that will be called when - FactoryFinder.getFactory(FACES_CONTEXT_FACTORY) is called. It must - be of type "ClassName". ---> -<!ELEMENT faces-context-factory (#PCDATA)> - -<!-- - The "from-action" element contains an action reference expression - that must have been executed (by the default ActionListener for handling - application level events) in order to select this navigation rule. If - not specified, this rule will be relevant no matter which action reference - was executed (or if no action reference was executed). - - This value must be of type "Action". ---> -<!ELEMENT from-action (#PCDATA)> - - -<!-- - The "from-outcome" element contains a logical outcome string returned - by the execution of an application action method selected via an - "actionRef" property (or a literal value specified by an "action" - property) of a UICommand component. If specified, this rule will be - relevant only if the outcome value matches this element's value. If - not specified, this rule will be relevant no matter what the outcome - value was. ---> -<!ELEMENT from-outcome (#PCDATA)> - - -<!-- - The "from-view-id" element contains the view identifier of the view - for which the containing navigation rule is relevant. If no - "from-view" element is specified, this rule applies to navigation - decisions on all views. If this element is not specified, a value - of "*" is assumed, meaning that this navigation rule applies to all - views. - - This value must be of type "ViewIdPattern". ---> -<!ELEMENT from-view-id (#PCDATA)> - - -<!-- - The "key" element is the String representation of a map key that - will be stored in a managed property of type java.util.Map. ---> -<!ELEMENT key (#PCDATA)> - - -<!-- - The "key-class" element defines the Java type to which each "key" - element in a set of "map-entry" elements will be converted to. It - must be of type "ClassName". If omitted, "java.lang.String" - is assumed. ---> -<!ELEMENT key-class (#PCDATA)> - - -<!-- - The "large-icon" element contains the resource path to a large (32x32) - icon image. The image may be in either GIF or JPG format. ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- - The "lifecycle-factory" element contains the fully qualified class name - of the concrete LifecycleFactory implementation class that will be called - when FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called. It must be - of type "ClassName". ---> -<!ELEMENT lifecycle-factory (#PCDATA)> - -<!-- - The "managed-bean-class" element represents the fully qualified class - name of the Java class that will be used to instantiate a new instance - if creation of the specified managed bean is requested. It must be of - type "ClassName". - - The specified class must conform to standard JavaBeans conventions. - In particular, it must have a public zero-arguments constructor, and - zero or more public property setters. ---> -<!ELEMENT managed-bean-class (#PCDATA)> - - -<!-- - The "managed-bean-name" element represents the attribute name under - which a managed bean will be searched for, as well as stored (unless - the "managed-bean-scope" value is "none"). It must be of type - "Identifier". ---> -<!ELEMENT managed-bean-name (#PCDATA)> - - -<!-- - The "managed-bean-scope" element represents the scope into which a newly - created instance of the specified managed bean will be stored (unless - the value is "none"). It must be of type "ScopeOrNone". ---> -<!ELEMENT managed-bean-scope (#PCDATA)> - -<!-- - The "navigation-handler" element contains the fully qualified class name - of the concrete NavigationHandler implementation class that will be called - during the Invoke Application phase of the request processing lifecycle, - if the default ActionListener (provided by the JSF implementation) is used. - It must be of type "ClassName". ---> -<!ELEMENT navigation-handler (#PCDATA)> - -<!-- -The "phase-listener" element contains the fully qualified class -name of the concrete PhaseListener implementation class that will be -registered on the Lifecycle. It must be of type "ClassName". ---> -<!ELEMENT phase-listener (#PCDATA)> - -<!-- - The "redirect" element indicates that navigation to the specified - "to-view-id" should be accomplished by performing an HTTP redirect - rather than the usual ViewHandler mechanisms. ---> -<!ELEMENT redirect EMPTY> - -<!-- - The "suggested-value" contains the value for the property or - attribute in which this element resides. This value is advisory - only and is intended for tools to use when populating pallettes. ---> -<!ELEMENT suggested-value (#PCDATA)> - - -<!-- - - The "view-handler" element contains the fully qualified class name - of the concrete ViewHandler implementation class that will be called - during the Restore View and Render Response phases of the request - processing lifecycle. The faces implementation must provide a - default implementation of this class ---> -<!ELEMENT view-handler (#PCDATA)> - -<!-- - - The "state-manager" element contains the fully qualified class name - of the concrete StateManager implementation class that will be called - during the Restore View and Render Response phases of the request - processing lifecycle. The faces implementation must provide a - default implementation of this class ---> -<!ELEMENT state-manager (#PCDATA)> - -<!-- - The "null-value" element indicates that the managed property in which we - are nested will be explicitly set to null if our managed bean is - automatically created. This is different from omitting the managed - property element entirely, which will cause no property setter to be - called for this property. - - The "null-value" element can only be used when the associated - "property-class" identifies a Java class, not a Java primitive. ---> -<!ELEMENT null-value EMPTY> - - -<!-- - The "property-class" element represents the Java type of the value - associated with this property name. It must be of type "JavaType". - If not specified, it can be inferred from existing classes; however, - this element should be specified if the configuration file is going - to be the source for generating the corresponding classes. ---> -<!ELEMENT property-class (#PCDATA)> - - -<!-- - The "property-name" element represents the JavaBeans property name - under which the corresponding value may be stored. ---> -<!ELEMENT property-name (#PCDATA)> - - -<!-- - The "property-resolver" element contains the fully qualified class name - of the concrete PropertyResolver implementation class that will be used - during the processing of value binding expressions. - It must be of type "ClassName". ---> -<!ELEMENT property-resolver (#PCDATA)> - - -<!-- - The "referenced-bean-class" element represents the fully qualified class - name of the Java class (either abstract or concrete) or Java interface - implemented by the corresponding referenced bean. It must be of type - "ClassName". ---> -<!ELEMENT referenced-bean-class (#PCDATA)> - - -<!-- - The "referenced-bean-name" element represents the attribute name under - which the corresponding referenced bean may be assumed to be stored, - in one of the scopes defined by the "Scope" type. It must be of type - "Identifier". ---> -<!ELEMENT referenced-bean-name (#PCDATA)> - - -<!-- - The "render-kit-id" element represents an identifier for the - RenderKit represented by the parent "render-kit" element. ---> -<!ELEMENT render-kit-id (#PCDATA)> - - -<!-- - The "render-kit-class" element represents the fully qualified class name - of a concrete RenderKit implementation class. It must be of - type "ClassName". ---> -<!ELEMENT render-kit-class (#PCDATA)> - - -<!-- - The "renderer-class" element represents the fully qualified class name - of a concrete Renderer implementation class. It must be of - type "ClassName". ---> -<!ELEMENT renderer-class (#PCDATA)> - -<!-- - The "render-kit-factory" element contains the fully qualified class name - of the concrete RenderKitFactory implementation class that will be called - when FactoryFinder.getFactory(RENDER_KIT_FACTORY) is called. It must be - of type "ClassName". ---> -<!ELEMENT render-kit-factory (#PCDATA)> - -<!-- - The "renderer-type" element represents a renderer type identifier for the - Renderer represented by the parent "renderer" element. ---> -<!ELEMENT renderer-type (#PCDATA)> - -<!-- - The "small-icon" element contains the resource path to a large (16x16) - icon image. The image may be in either GIF or JPG format. ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- - The "supported-locale" element allows authors to declare which - locales are supported in this application instance. - - It must be specified as :language:[_:country:[_:variant:]] without - the colons, for example "ja_JP_SJIS". The separators between the - segments may be '-' or '_'. ---> -<!ELEMENT supported-locale (#PCDATA)> - -<!-- - The "to-view" element contains the view identifier of the next view - that should be displayed if this navigation rule is matched. It - must be of type "ViewId". ---> -<!ELEMENT to-view-id (#PCDATA)> - - -<!-- - The "validator-class" element represents the fully qualified class name - of a concrete Validator implementation class. It must be of - type "ClassName". ---> -<!ELEMENT validator-class (#PCDATA)> - - -<!-- - The "validator-id" element represents the identifier under which the - corresponding Validator class should be registered. ---> -<!ELEMENT validator-id (#PCDATA)> - - -<!-- - The "value" element is the String representation of a literal - value to which a scalar managed property will be set, or a value - binding expression ("#{...}") that will be used to calculate the - required value. It will be converted as specified for the actual - property type. ---> -<!ELEMENT value (#PCDATA)> - - -<!-- - The "value-class" element defines the Java type to which each - "value" element's value will be converted to, prior to adding it to - the "list-entries" list for a managed property that is a - java.util.List, or a "map-entries" map for a managed property that - is a java.util.Map. It must be of type "ClassName". If omitted, - "java.lang.String" is assumed. ---> -<!ELEMENT value-class (#PCDATA)> - -<!-- - The "variable-resolver" element contains the fully qualified class name - of the concrete VariableResolver implementation class that will be used - during the processing of value binding expressions. - It must be of type "ClassName". ---> -<!ELEMENT variable-resolver (#PCDATA)> - - -<!-- ============================ Identifier Attributes ==================== --> - - -<!ATTLIST action-listener id ID #IMPLIED> -<!ATTLIST application id ID #IMPLIED> -<!ATTLIST application-factory id ID #IMPLIED> -<!ATTLIST attribute id ID #IMPLIED> -<!ATTLIST attribute-class id ID #IMPLIED> -<!ATTLIST attribute-extension id ID #IMPLIED> -<!ATTLIST attribute-name id ID #IMPLIED> -<!ATTLIST component id ID #IMPLIED> -<!ATTLIST component-class id ID #IMPLIED> -<!ATTLIST component-extension id ID #IMPLIED> -<!ATTLIST component-family id ID #IMPLIED> -<!ATTLIST component-type id ID #IMPLIED> -<!ATTLIST converter id ID #IMPLIED> -<!ATTLIST converter-class id ID #IMPLIED> -<!ATTLIST converter-for-class id ID #IMPLIED> -<!ATTLIST converter-id id ID #IMPLIED> -<!ATTLIST default-locale id ID #IMPLIED> -<!ATTLIST default-render-kit-id id ID #IMPLIED> -<!ATTLIST default-value id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST faces-config id ID #IMPLIED> -<!ATTLIST faces-context-factory id ID #IMPLIED> -<!ATTLIST factory id ID #IMPLIED> -<!ATTLIST from-action id ID #IMPLIED> -<!ATTLIST from-outcome id ID #IMPLIED> -<!ATTLIST from-view-id id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST key id ID #IMPLIED> -<!ATTLIST key-class id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST lifecycle id ID #IMPLIED> -<!ATTLIST lifecycle-factory id ID #IMPLIED> -<!ATTLIST list-entries id ID #IMPLIED> -<!ATTLIST locale-config id ID #IMPLIED> -<!ATTLIST managed-bean id ID #IMPLIED> -<!ATTLIST managed-bean-class id ID #IMPLIED> -<!ATTLIST managed-bean-name id ID #IMPLIED> -<!ATTLIST managed-bean-scope id ID #IMPLIED> -<!ATTLIST managed-property id ID #IMPLIED> -<!ATTLIST map-entries id ID #IMPLIED> -<!ATTLIST map-entry id ID #IMPLIED> -<!ATTLIST message-bundle id ID #IMPLIED> -<!ATTLIST navigation-case id ID #IMPLIED> -<!ATTLIST navigation-handler id ID #IMPLIED> -<!ATTLIST navigation-rule id ID #IMPLIED> -<!ATTLIST null-value id ID #IMPLIED> -<!ATTLIST phase-listener id ID #IMPLIED> -<!ATTLIST property id ID #IMPLIED> -<!ATTLIST property-class id ID #IMPLIED> -<!ATTLIST property-extension id ID #IMPLIED> -<!ATTLIST property-name id ID #IMPLIED> -<!ATTLIST property-resolver id ID #IMPLIED> -<!ATTLIST redirect id ID #IMPLIED> -<!ATTLIST referenced-bean id ID #IMPLIED> -<!ATTLIST referenced-bean-class id ID #IMPLIED> -<!ATTLIST referenced-bean-name id ID #IMPLIED> -<!ATTLIST render-kit id ID #IMPLIED> -<!ATTLIST render-kit-class id ID #IMPLIED> -<!ATTLIST render-kit-factory id ID #IMPLIED> -<!ATTLIST render-kit-id id ID #IMPLIED> -<!ATTLIST renderer id ID #IMPLIED> -<!ATTLIST renderer-class id ID #IMPLIED> -<!ATTLIST renderer-extension id ID #IMPLIED> -<!ATTLIST renderer-type id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST state-manager id ID #IMPLIED> -<!ATTLIST suggested-value id ID #IMPLIED> -<!ATTLIST supported-locale id ID #IMPLIED> -<!ATTLIST to-view-id id ID #IMPLIED> -<!ATTLIST validator id ID #IMPLIED> -<!ATTLIST validator-class id ID #IMPLIED> -<!ATTLIST validator-id id ID #IMPLIED> -<!ATTLIST value id ID #IMPLIED> -<!ATTLIST value-class id ID #IMPLIED> -<!ATTLIST variable-resolver id ID #IMPLIED> -<!ATTLIST view-handler id ID #IMPLIED> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_1.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_1.dtd deleted file mode 100644 index 03dad8e2e6..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_1.dtd +++ /dev/null @@ -1,895 +0,0 @@ -<!-- - DTD for the JavaServer Faces Application Configuration File (Version 1.1) - - To support validation of your configuration file(s), include the following - DOCTYPE element at the beginning (after the "xml" declaration): - - <!DOCTYPE faces-config PUBLIC - "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN" - "http://java.sun.com/dtd/web-facesconfig_1_1.dtd"> - - $Id: web-facesconfig_1_1.dtd,v 1.1 2007/05/25 21:12:48 david_williams Exp $ - ---> - - -<!-- ==================== Defined Types =================================== --> - - -<!-- - An "Action" is a String that represents a method binding - expression that points at a method with no arguments that returns a - String. It must be bracketed with "#{}", for example, - "#{cardemo.buyCar}". ---> -<!ENTITY % Action "CDATA"> - - -<!-- - A "ClassName" is the fully qualified name of a Java class that is - instantiated to provide the functionality of the enclosing element. ---> -<!ENTITY % ClassName "CDATA"> - - -<!-- - An "Identifier" is a string of characters that conforms to the variable - naming conventions of the Java programming language (JLS Section ?.?.?). ---> -<!ENTITY % Identifier "CDATA"> - - -<!-- - A "JavaType" is either the fully qualified name of a Java class that is - instantiated to provide the functionality of the enclosing element, or - the name of a Java primitive type (such as int or char). The class name - or primitive type may optionally be followed by "[]" to indicate that - the underlying data must be an array, rather than a scalar variable. ---> -<!ENTITY % JavaType "CDATA"> - - -<!-- - A "Language" is a lower case two-letter code for a language as defined - by ISL-639. ---> -<!ENTITY % Language "CDATA"> - - -<!-- - A "ResourcePath" is the relative or absolute path to a resource file - (such as a logo image). ---> -<!ENTITY % ResourcePath "CDATA"> - - -<!-- - A "Scope" is the well-known name of a scope in which managed beans may - optionally be defined to be created in. ---> -<!ENTITY % Scope "(request|session|application)"> - - - -<!-- - A "ScopeOrNone" element defines the legal values for the - <managed-bean-scope> element's body content, which includes - all of the scopes respresented by the "Scope" type, plus the - "none" value indicating that a created bean should not be - stored into any scope. ---> -<!ENTITY % ScopeOrNone "(request|session|application|none)"> - - -<!-- - A "ViewIdPattern" is a pattern for matching view identifiers in - order to determine whether a particular navigation rule should be - fired. It must contain one of the following values: - - - The exact match for a view identifier that is recognized - by the the ViewHandler implementation being used (such as - "/index.jsp" if you are using the default ViewHandler). - - - A proper prefix of a view identifier, plus a trailing "*" - character. This pattern indicates that all view identifiers that - match the portion of the pattern up to the asterisk will match the - surrounding rule. When more than one match exists, the match with - the longest pattern is selected. - - - An "*" character, which means that this pattern applies to all - view identifiers. ---> -<!ENTITY % ViewIdPattern "CDATA"> - - -<!-- ==================== Top Level Elements ============================== --> - - -<!-- - The "faces-config" element is the root of the configuration information - hierarchy, and contains nested elements for all of the other configuration - settings. ---> -<!ELEMENT faces-config ((application|factory|component|converter|managed-bean|navigation-rule|referenced-bean|render-kit|lifecycle|validator)*)> -<!ATTLIST faces-config - xmlns CDATA #FIXED "http://java.sun.com/JSF/Configuration"> - - - -<!-- ==================== Definition Elements ============================= --> - - -<!-- - The "application" element provides a mechanism to define the various - per-application-singleton implementation artifacts for a particular web - application that is utilizing JavaServer Faces. For nested elements - that are not specified, the JSF implementation must provide a suitable - default. ---> -<!ELEMENT application ((action-listener|default-render-kit-id|message-bundle|navigation-handler|view-handler|state-manager|property-resolver|variable-resolver|locale-config)*)> - - -<!-- - The "factory" element provides a mechanism to define the various - Factories that comprise parts of the implementation of JavaServer - Faces. For nested elements that are not specified, the JSF - implementation must provide a suitable default. ---> -<!ELEMENT factory ((application-factory|faces-context-factory|lifecycle-factory|render-kit-factory)*)> - - -<!-- - The "attribute" element represents a named, typed, value associated with - the parent UIComponent via the generic attributes mechanism. - - Attribute names must be unique within the scope of the parent (or related) - component. ---> -<!ELEMENT attribute (description*, display-name*, icon*, attribute-name, attribute-class, default-value?, suggested-value?, attribute-extension*)> - -<!-- - Extension element for attribute. May contain implementation - specific content. ---> -<!ELEMENT attribute-extension ANY> - - -<!-- - The "component" element represents a concrete UIComponent implementation - class that should be registered under the specified type identifier, - along with its associated properties and attributes. Component types must - be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that are recognized - by the implementation logic of this component. Nested "property" elements - identify JavaBeans properties of the component class that may be exposed - for manipulation via tools. ---> -<!ELEMENT component (description*, display-name*, icon*, component-type, component-class, facet*, attribute*, property*, component-extension*)> - -<!-- - Extension element for component. May contain implementation - specific content. ---> -<!ELEMENT component-extension ANY> - -<!-- - Define the name and other design-time information for a facet that is - associated with a renderer or a component. ---> - -<!ELEMENT facet (description*, display-name*, icon*, facet-name, facet-extension*)> - -<!-- - Extension element for facet. May contain implementation - specific content. ---> -<!ELEMENT facet-extension ANY> - -<!-- - The "facet-name" element represents the facet name under which a - UIComponent will be added to its parent. It must be of type - "Identifier". ---> -<!ELEMENT facet-name (#PCDATA)> - -<!-- - The "converter" element represents a concrete Converter implementation - class that should be registered under the specified converter identifier. - Converter identifiers must be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that may be - configured on the corresponding UIComponent in order to affect the - operation of the Converter. Nested "property" elements identify JavaBeans - properties of the Converter implementation class that may be configured - to affect the operation of the Converter. ---> -<!ELEMENT converter (description*, display-name*, icon*, (converter-id | converter-for-class), converter-class, attribute*, property*)> - - -<!-- - The "icon" element contains "small-icon" and "large-icon" elements that - specify the resoruce paths for small and large GIF or JPG icon images - used to represent the parent element in a GUI tool. ---> -<!ELEMENT icon (small-icon?, large-icon?)> -<!ATTLIST icon xml:lang %Language; #IMPLIED> - -<!-- - The "lifecycle" element provides a mechanism to specify - modifications to the behaviour of the default Lifecycle - implementation for this web application. ---> -<!ELEMENT lifecycle (phase-listener*)> - -<!-- - The "locale-config" element allows the app developer to declare the - supported locales for this application. ---> -<!ELEMENT locale-config (default-locale?, supported-locale*)> - -<!-- - The "managed-bean" element represents a JavaBean, of a particular class, - that will be dynamically instantiated at runtime (by the default - VariableResolver implementation) if it is referenced as the first element - of a value binding expression, and no corresponding bean can be - identified in any scope. In addition to the creation of the managed bean, - and the optional storing of it into the specified scope, the nested - managed-property elements can be used to initialize the contents of - settable JavaBeans properties of the created instance. ---> -<!ELEMENT managed-bean (description*, display-name*, icon*, managed-bean-name, managed-bean-class, managed-bean-scope, (managed-property* | map-entries | list-entries))> - - -<!-- - The "managed-property" element represents an individual property of a - managed bean that will be configured to the specified value (or value set) - if the corresponding managed bean is automatically created. ---> -<!ELEMENT managed-property (description*, display-name*, icon*, property-name, property-class?, (map-entries|null-value|value|list-entries))> - - -<!-- - The "map-entry" element reprsents a single key-entry pair that - will be added to the computed value of a managed property of type - java.util.Map. ---> -<!ELEMENT map-entry (key, (null-value|value))> - - -<!-- - The "map-entries' element represents a set of key-entry pairs that - will be added to the computed value of a managed property of type - java.util.Map. In addition, the Java class types of the key and entry - values may be optionally declared. ---> -<!ELEMENT map-entries (key-class?, value-class?, map-entry*)> - - -<!-- - The base name of a resource bundle representing the message resources - for this application. See the JavaDocs for the "java.util.ResourceBundle" - class for more information on the syntax of resource bundle names. ---> - -<!ELEMENT message-bundle (#PCDATA)> - - -<!-- - The "navigation-case" element describes a particular combination of - conditions that must match for this case to be executed, and the - view id of the component tree that should be selected next. ---> -<!ELEMENT navigation-case (description*, display-name*, icon*, from-action?, from-outcome?, to-view-id, redirect?)> - - -<!-- - The "navigation-rule" element represents an individual decision rule - that will be utilized by the default NavigationHandler - implementation to make decisions on what view should be displayed - next, based on the view id being processed. ---> -<!ELEMENT navigation-rule (description*, display-name*, icon*, from-view-id?, navigation-case*)> - - -<!-- - The "property" element represents a JavaBean property of the Java class - represented by our parent element. - - Property names must be unique within the scope of the Java class - that is represented by the parent element, and must correspond to - property names that will be recognized when performing introspection - against that class via java.beans.Introspector. ---> -<!ELEMENT property (description*, display-name*, icon*, property-name, property-class, default-value?, suggested-value?, property-extension*)> - -<!-- - Extension element for property. May contain implementation - specific content. ---> -<!ELEMENT property-extension ANY> - -<!-- - The "referenced-bean" element represents at design time the promise - that a Java object of the specified type will exist at runtime in some - scope, under the specified key. This can be used by design time tools - to construct user interface dialogs based on the properties of the - specified class. The presence or absence of a referenced bean - element has no impact on the JavaServer Faces runtime environment - inside a web application. ---> -<!ELEMENT referenced-bean (description*, display-name*, icon*, referenced-bean-name, referenced-bean-class)> - - -<!-- - The "render-kit" element represents a concrete RenderKit implementation - that should be registered under the specified render-kit-id. If no - render-kit-id is specified, the identifier of the default RenderKit - (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed. ---> -<!ELEMENT render-kit (description*, display-name*, icon*, render-kit-id?, render-kit-class?, renderer*)> - - -<!-- - The "renderer" element represents a concrete Renderer implementation - class that should be registered under the specified component family - and renderer type identifiers, in the RenderKit associated with the - parent "render-kit" element. Combinations of component family and renderer - type must be unique within the RenderKit associated with the parent - "render-kit" element. - - Nested "attribute" elements identify generic component attributes that - are recognized by this renderer. ---> -<!ELEMENT renderer (description*, display-name*, icon*, component-family, renderer-type, renderer-class, facet*, attribute*, renderer-extension*)> - -<!-- - Extension element for renderer. May contain implementation - specific content. ---> -<!ELEMENT renderer-extension ANY> - -<!-- - The "validator" element represents a concrete Validator implementation - class that should be registered under the specified validator identifier. - Validator identifiers must be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that may be - configured on the corresponding UIComponent in order to affect the - operation of the Validator. Nested "property" elements identify JavaBeans - properties of the Validator implementation class that may be configured - to affect the operation of the Validator. ---> -<!ELEMENT validator (description*, display-name*, icon*, validator-id, validator-class, attribute*, property*)> - - -<!-- - The "list-entries" element represents a set of initialization - elements for a managed property that is a java.util.List or an - array. In the former case, the "value-class" element can optionally - be used to declare the Java type to which each value should be - converted before adding it to the Collection. ---> -<!ELEMENT list-entries (value-class?, (null-value|value)*)> - - -<!-- ==================== Subordinate Elements ============================ --> - - -<!-- - The "action-listener" element contains the fully qualified class name - of the concrete ActionListener implementation class that will be called - during the Invoke Application phase of the request processing lifecycle. - It must be of type "ClassName". ---> -<!ELEMENT action-listener (#PCDATA)> - -<!-- - The "application-factory" element contains the fully qualified class - name of the concrete ApplicationFactory implementation class that - will be called when FactoryFinder.getFactory(APPLICATION_FACTORY) is - called. It must be of type "ClassName". ---> -<!ELEMENT application-factory (#PCDATA)> - -<!-- - The "attribute-class" element represents the Java type of the value - associated with this attribute name. It must be of type "ClassName". ---> -<!ELEMENT attribute-class (#PCDATA)> - - -<!-- - The "attribute-name" element represents the name under which the - corresponding value will be stored, in the generic attributes of the - UIComponent we are related to. ---> -<!ELEMENT attribute-name (#PCDATA)> - - -<!-- - The "component-class" element represents the fully qualified class name - of a concrete UIComponent implementation class. It must be of - type "ClassName". ---> -<!ELEMENT component-class (#PCDATA)> - - -<!-- - The "component-family" element represents the component family for - which the Renderer represented by the parent "renderer" element will be - used. ---> -<!ELEMENT component-family (#PCDATA)> - -<!-- - The "component-type" element represents the name under which the - corresponding UIComponent class should be registered. ---> -<!ELEMENT component-type (#PCDATA)> - - -<!-- - The "converter-class" element represents the fully qualified class name - of a concrete Converter implementation class. It must be of - type "ClassName". ---> -<!ELEMENT converter-class (#PCDATA)> - - -<!-- - The "converter-for-class" element represents the fully qualified class name - for which a Converter class will be registered. It must be of - type "ClassName". ---> -<!ELEMENT converter-for-class (#PCDATA)> - - -<!-- - The "converter-id" element represents the identifier under which the - corresponding Converter class should be registered. ---> -<!ELEMENT converter-id (#PCDATA)> - -<!-- - The "default-render-kit-id" element allows the application to define - a renderkit to be used other than the standard one. ---> -<!ELEMENT default-render-kit-id (#PCDATA)> - -<!-- - The "default-locale" element declares the default locale for this - application instance. It must be specified as - :language:[_:country:[_:variant:]] without the colons, for example - "ja_JP_SJIS". The separators between the segments may be '-' or - '_'. ---> -<!ELEMENT default-locale (#PCDATA)> - -<!-- - The "default-value" contains the value for the property or attribute - in which this element resides. This value differs from the - "suggested-value" in that the property or attribute must take the - value, whereas in "suggested-value" taking the value is optional. ---> -<!ELEMENT default-value (#PCDATA)> - -<!-- - The "description" element contains a textual description of the element - it is nested in, optionally flagged with a language code using the - "xml:lang" attribute. ---> -<!ELEMENT description ANY> -<!ATTLIST description xml:lang %Language; #IMPLIED> - - -<!-- - The "display-name" element is a short descriptive name describing the - entity associated with the element it is nested in, intended to be - displayed by tools, and optionally flagged with a language code using - the "xml:lang" attribute. ---> -<!ELEMENT display-name (#PCDATA)> -<!ATTLIST display-name xml:lang %Language; #IMPLIED> - -<!-- - The "faces-context-factory" element contains the fully qualified - class name of the concrete FacesContextFactory implementation class - that will be called when - FactoryFinder.getFactory(FACES_CONTEXT_FACTORY) is called. It must - be of type "ClassName". ---> -<!ELEMENT faces-context-factory (#PCDATA)> - -<!-- - The "from-action" element contains an action reference expression - that must have been executed (by the default ActionListener for handling - application level events) in order to select this navigation rule. If - not specified, this rule will be relevant no matter which action reference - was executed (or if no action reference was executed). - - This value must be of type "Action". ---> -<!ELEMENT from-action (#PCDATA)> - - -<!-- - The "from-outcome" element contains a logical outcome string returned - by the execution of an application action method selected via an - "actionRef" property (or a literal value specified by an "action" - property) of a UICommand component. If specified, this rule will be - relevant only if the outcome value matches this element's value. If - not specified, this rule will be relevant no matter what the outcome - value was. ---> -<!ELEMENT from-outcome (#PCDATA)> - - -<!-- - The "from-view-id" element contains the view identifier of the view - for which the containing navigation rule is relevant. If no - "from-view" element is specified, this rule applies to navigation - decisions on all views. If this element is not specified, a value - of "*" is assumed, meaning that this navigation rule applies to all - views. - - This value must be of type "ViewIdPattern". ---> -<!ELEMENT from-view-id (#PCDATA)> - - -<!-- - The "key" element is the String representation of a map key that - will be stored in a managed property of type java.util.Map. ---> -<!ELEMENT key (#PCDATA)> - - -<!-- - The "key-class" element defines the Java type to which each "key" - element in a set of "map-entry" elements will be converted to. It - must be of type "ClassName". If omitted, "java.lang.String" - is assumed. ---> -<!ELEMENT key-class (#PCDATA)> - - -<!-- - The "large-icon" element contains the resource path to a large (32x32) - icon image. The image may be in either GIF or JPG format. ---> -<!ELEMENT large-icon (#PCDATA)> - -<!-- - The "lifecycle-factory" element contains the fully qualified class name - of the concrete LifecycleFactory implementation class that will be called - when FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called. It must be - of type "ClassName". ---> -<!ELEMENT lifecycle-factory (#PCDATA)> - -<!-- - The "managed-bean-class" element represents the fully qualified class - name of the Java class that will be used to instantiate a new instance - if creation of the specified managed bean is requested. It must be of - type "ClassName". - - The specified class must conform to standard JavaBeans conventions. - In particular, it must have a public zero-arguments constructor, and - zero or more public property setters. ---> -<!ELEMENT managed-bean-class (#PCDATA)> - - -<!-- - The "managed-bean-name" element represents the attribute name under - which a managed bean will be searched for, as well as stored (unless - the "managed-bean-scope" value is "none"). It must be of type - "Identifier". ---> -<!ELEMENT managed-bean-name (#PCDATA)> - - -<!-- - The "managed-bean-scope" element represents the scope into which a newly - created instance of the specified managed bean will be stored (unless - the value is "none"). It must be of type "ScopeOrNone". ---> -<!ELEMENT managed-bean-scope (#PCDATA)> - -<!-- - The "navigation-handler" element contains the fully qualified class name - of the concrete NavigationHandler implementation class that will be called - during the Invoke Application phase of the request processing lifecycle, - if the default ActionListener (provided by the JSF implementation) is used. - It must be of type "ClassName". ---> -<!ELEMENT navigation-handler (#PCDATA)> - -<!-- -The "phase-listener" element contains the fully qualified class -name of the concrete PhaseListener implementation class that will be -registered on the Lifecycle. It must be of type "ClassName". ---> -<!ELEMENT phase-listener (#PCDATA)> - -<!-- - The "redirect" element indicates that navigation to the specified - "to-view-id" should be accomplished by performing an HTTP redirect - rather than the usual ViewHandler mechanisms. ---> -<!ELEMENT redirect EMPTY> - -<!-- - The "suggested-value" contains the value for the property or - attribute in which this element resides. This value is advisory - only and is intended for tools to use when populating pallettes. ---> -<!ELEMENT suggested-value (#PCDATA)> - - -<!-- - - The "view-handler" element contains the fully qualified class name - of the concrete ViewHandler implementation class that will be called - during the Restore View and Render Response phases of the request - processing lifecycle. The faces implementation must provide a - default implementation of this class ---> -<!ELEMENT view-handler (#PCDATA)> - -<!-- - - The "state-manager" element contains the fully qualified class name - of the concrete StateManager implementation class that will be called - during the Restore View and Render Response phases of the request - processing lifecycle. The faces implementation must provide a - default implementation of this class ---> -<!ELEMENT state-manager (#PCDATA)> - -<!-- - The "null-value" element indicates that the managed property in which we - are nested will be explicitly set to null if our managed bean is - automatically created. This is different from omitting the managed - property element entirely, which will cause no property setter to be - called for this property. - - The "null-value" element can only be used when the associated - "property-class" identifies a Java class, not a Java primitive. ---> -<!ELEMENT null-value EMPTY> - - -<!-- - The "property-class" element represents the Java type of the value - associated with this property name. It must be of type "JavaType". - If not specified, it can be inferred from existing classes; however, - this element should be specified if the configuration file is going - to be the source for generating the corresponding classes. ---> -<!ELEMENT property-class (#PCDATA)> - - -<!-- - The "property-name" element represents the JavaBeans property name - under which the corresponding value may be stored. ---> -<!ELEMENT property-name (#PCDATA)> - - -<!-- - The "property-resolver" element contains the fully qualified class name - of the concrete PropertyResolver implementation class that will be used - during the processing of value binding expressions. - It must be of type "ClassName". ---> -<!ELEMENT property-resolver (#PCDATA)> - - -<!-- - The "referenced-bean-class" element represents the fully qualified class - name of the Java class (either abstract or concrete) or Java interface - implemented by the corresponding referenced bean. It must be of type - "ClassName". ---> -<!ELEMENT referenced-bean-class (#PCDATA)> - - -<!-- - The "referenced-bean-name" element represents the attribute name under - which the corresponding referenced bean may be assumed to be stored, - in one of the scopes defined by the "Scope" type. It must be of type - "Identifier". ---> -<!ELEMENT referenced-bean-name (#PCDATA)> - - -<!-- - The "render-kit-id" element represents an identifier for the - RenderKit represented by the parent "render-kit" element. ---> -<!ELEMENT render-kit-id (#PCDATA)> - - -<!-- - The "render-kit-class" element represents the fully qualified class name - of a concrete RenderKit implementation class. It must be of - type "ClassName". ---> -<!ELEMENT render-kit-class (#PCDATA)> - - -<!-- - The "renderer-class" element represents the fully qualified class name - of a concrete Renderer implementation class. It must be of - type "ClassName". ---> -<!ELEMENT renderer-class (#PCDATA)> - -<!-- - The "render-kit-factory" element contains the fully qualified class name - of the concrete RenderKitFactory implementation class that will be called - when FactoryFinder.getFactory(RENDER_KIT_FACTORY) is called. It must be - of type "ClassName". ---> -<!ELEMENT render-kit-factory (#PCDATA)> - -<!-- - The "renderer-type" element represents a renderer type identifier for the - Renderer represented by the parent "renderer" element. ---> -<!ELEMENT renderer-type (#PCDATA)> - -<!-- - The "small-icon" element contains the resource path to a large (16x16) - icon image. The image may be in either GIF or JPG format. ---> -<!ELEMENT small-icon (#PCDATA)> - -<!-- - The "supported-locale" element allows authors to declare which - locales are supported in this application instance. - - It must be specified as :language:[_:country:[_:variant:]] without - the colons, for example "ja_JP_SJIS". The separators between the - segments may be '-' or '_'. ---> -<!ELEMENT supported-locale (#PCDATA)> - -<!-- - The "to-view" element contains the view identifier of the next view - that should be displayed if this navigation rule is matched. It - must be of type "ViewId". ---> -<!ELEMENT to-view-id (#PCDATA)> - - -<!-- - The "validator-class" element represents the fully qualified class name - of a concrete Validator implementation class. It must be of - type "ClassName". ---> -<!ELEMENT validator-class (#PCDATA)> - - -<!-- - The "validator-id" element represents the identifier under which the - corresponding Validator class should be registered. ---> -<!ELEMENT validator-id (#PCDATA)> - - -<!-- - The "value" element is the String representation of a literal - value to which a scalar managed property will be set, or a value - binding expression ("#{...}") that will be used to calculate the - required value. It will be converted as specified for the actual - property type. ---> -<!ELEMENT value (#PCDATA)> - - -<!-- - The "value-class" element defines the Java type to which each - "value" element's value will be converted to, prior to adding it to - the "list-entries" list for a managed property that is a - java.util.List, or a "map-entries" map for a managed property that - is a java.util.Map. It must be of type "ClassName". If omitted, - "java.lang.String" is assumed. ---> -<!ELEMENT value-class (#PCDATA)> - -<!-- - The "variable-resolver" element contains the fully qualified class name - of the concrete VariableResolver implementation class that will be used - during the processing of value binding expressions. - It must be of type "ClassName". ---> -<!ELEMENT variable-resolver (#PCDATA)> - - -<!-- ============================ Identifier Attributes ==================== --> - - -<!ATTLIST action-listener id ID #IMPLIED> -<!ATTLIST application id ID #IMPLIED> -<!ATTLIST application-factory id ID #IMPLIED> -<!ATTLIST attribute id ID #IMPLIED> -<!ATTLIST attribute-class id ID #IMPLIED> -<!ATTLIST attribute-extension id ID #IMPLIED> -<!ATTLIST attribute-name id ID #IMPLIED> -<!ATTLIST component id ID #IMPLIED> -<!ATTLIST component-class id ID #IMPLIED> -<!ATTLIST component-extension id ID #IMPLIED> -<!ATTLIST component-family id ID #IMPLIED> -<!ATTLIST component-type id ID #IMPLIED> -<!ATTLIST converter id ID #IMPLIED> -<!ATTLIST converter-class id ID #IMPLIED> -<!ATTLIST converter-for-class id ID #IMPLIED> -<!ATTLIST converter-id id ID #IMPLIED> -<!ATTLIST default-locale id ID #IMPLIED> -<!ATTLIST default-render-kit-id id ID #IMPLIED> -<!ATTLIST default-value id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST display-name id ID #IMPLIED> -<!ATTLIST faces-config id ID #IMPLIED> -<!ATTLIST faces-context-factory id ID #IMPLIED> -<!ATTLIST facet id ID #IMPLIED> -<!ATTLIST facet-extension id ID #IMPLIED> -<!ATTLIST facet-name id ID #IMPLIED> -<!ATTLIST factory id ID #IMPLIED> -<!ATTLIST from-action id ID #IMPLIED> -<!ATTLIST from-outcome id ID #IMPLIED> -<!ATTLIST from-view-id id ID #IMPLIED> -<!ATTLIST icon id ID #IMPLIED> -<!ATTLIST key id ID #IMPLIED> -<!ATTLIST key-class id ID #IMPLIED> -<!ATTLIST large-icon id ID #IMPLIED> -<!ATTLIST lifecycle id ID #IMPLIED> -<!ATTLIST lifecycle-factory id ID #IMPLIED> -<!ATTLIST list-entries id ID #IMPLIED> -<!ATTLIST locale-config id ID #IMPLIED> -<!ATTLIST managed-bean id ID #IMPLIED> -<!ATTLIST managed-bean-class id ID #IMPLIED> -<!ATTLIST managed-bean-name id ID #IMPLIED> -<!ATTLIST managed-bean-scope id ID #IMPLIED> -<!ATTLIST managed-property id ID #IMPLIED> -<!ATTLIST map-entries id ID #IMPLIED> -<!ATTLIST map-entry id ID #IMPLIED> -<!ATTLIST message-bundle id ID #IMPLIED> -<!ATTLIST navigation-case id ID #IMPLIED> -<!ATTLIST navigation-handler id ID #IMPLIED> -<!ATTLIST navigation-rule id ID #IMPLIED> -<!ATTLIST null-value id ID #IMPLIED> -<!ATTLIST phase-listener id ID #IMPLIED> -<!ATTLIST property id ID #IMPLIED> -<!ATTLIST property-class id ID #IMPLIED> -<!ATTLIST property-extension id ID #IMPLIED> -<!ATTLIST property-name id ID #IMPLIED> -<!ATTLIST property-resolver id ID #IMPLIED> -<!ATTLIST redirect id ID #IMPLIED> -<!ATTLIST referenced-bean id ID #IMPLIED> -<!ATTLIST referenced-bean-class id ID #IMPLIED> -<!ATTLIST referenced-bean-name id ID #IMPLIED> -<!ATTLIST render-kit id ID #IMPLIED> -<!ATTLIST render-kit-class id ID #IMPLIED> -<!ATTLIST render-kit-factory id ID #IMPLIED> -<!ATTLIST render-kit-id id ID #IMPLIED> -<!ATTLIST renderer id ID #IMPLIED> -<!ATTLIST renderer-class id ID #IMPLIED> -<!ATTLIST renderer-extension id ID #IMPLIED> -<!ATTLIST renderer-type id ID #IMPLIED> -<!ATTLIST small-icon id ID #IMPLIED> -<!ATTLIST state-manager id ID #IMPLIED> -<!ATTLIST suggested-value id ID #IMPLIED> -<!ATTLIST supported-locale id ID #IMPLIED> -<!ATTLIST to-view-id id ID #IMPLIED> -<!ATTLIST validator id ID #IMPLIED> -<!ATTLIST validator-class id ID #IMPLIED> -<!ATTLIST validator-id id ID #IMPLIED> -<!ATTLIST value id ID #IMPLIED> -<!ATTLIST value-class id ID #IMPLIED> -<!ATTLIST variable-resolver id ID #IMPLIED> -<!ATTLIST view-handler id ID #IMPLIED> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_2.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_2.xsd deleted file mode 100644 index de857f0f0c..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-facesconfig_1_2.xsd +++ /dev/null @@ -1,2071 +0,0 @@ -<?xml version = "1.0" encoding = "UTF-8"?> - -<xsd:schema - 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" - xmlns:xml="http://www.w3.org/XML/1998/namespace" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="1.2"> - - <xsd:annotation> - <xsd:documentation> - $Id: web-facesconfig_1_2.xsd,v 1.1 2007/05/25 21:12:49 david_williams Exp $ - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2005 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, Java EE, - 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[ - - The XML Schema for the JavaServer Faces Application - Configuration File (Version 1.2). - - All JavaServer Faces configuration files must indicate - the JavaServer Faces schema by indicating the JavaServer - Faces namespace: - - http://java.sun.com/xml/ns/javaee - - and by indicating the version of the schema by - using the version element as shown below: - - <faces-config xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="..." - version="1.2"> - ... - </faces-config> - - The instance documents may indicate the published - version of the schema using xsi:schemaLocation attribute - for javaee namespace with the following location: - - http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd - - ]]> - - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="javaee_5.xsd"/> - - <!-- **************************************************** --> - - <xsd:element name = "faces-config" type="javaee:faces-configType"> - <xsd:annotation> - <xsd:documentation> - - The "faces-config" element is the root of the configuration - information hierarchy, and contains nested elements for all - of the other configuration settings. - - </xsd:documentation> - </xsd:annotation> - - <xsd:unique name="faces-config-converter-ID-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - Converter IDs must be unique within a document. - - </xsd:documentation> - </xsd:annotation> - - <xsd:selector xpath="javaee:converter"/> - <xsd:field xpath="javaee:converter-id"/> - </xsd:unique> - - <xsd:unique name="faces-config-converter-for-class-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - 'converter-for-class' element values must be unique - within a document. - - </xsd:documentation> - </xsd:annotation> - - <xsd:selector xpath="javaee:converter"/> - <xsd:field xpath="javaee:converter-for-class"/> - </xsd:unique> - - <xsd:unique name="faces-config-validator-ID-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - Validator IDs must be unique within a document. - - </xsd:documentation> - </xsd:annotation> - - <xsd:selector xpath="javaee:validator"/> - <xsd:field xpath="javaee:validator-id"/> - </xsd:unique> - - <xsd:unique name="faces-config-managed-bean-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - Managed bean names must be unique within a document. - - </xsd:documentation> - </xsd:annotation> - - <xsd:selector xpath="javaee:managed-bean"/> - <xsd:field xpath="javaee:managed-bean-name"/> - </xsd:unique> - </xsd:element> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-configType"> - <xsd:annotation> - <xsd:documentation> - - The "faces-config" element is the root of the configuration - information hierarchy, and contains nested elements for all - of the other configuration settings. - - </xsd:documentation> - </xsd:annotation> - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:element name="application" - type="javaee:faces-config-applicationType"/> - <xsd:element name="factory" - type="javaee:faces-config-factoryType"/> - <xsd:element name="component" - type="javaee:faces-config-componentType"/> - <xsd:element name="converter" - type="javaee:faces-config-converterType"/> - <xsd:element name="managed-bean" - type="javaee:faces-config-managed-beanType"/> - <xsd:element name="navigation-rule" - type="javaee:faces-config-navigation-ruleType"/> - <xsd:element name="referenced-bean" - type="javaee:faces-config-referenced-beanType"/> - <xsd:element name="render-kit" - type="javaee:faces-config-render-kitType"/> - <xsd:element name="lifecycle" - type="javaee:faces-config-lifecycleType"/> - <xsd:element name="validator" - type="javaee:faces-config-validatorType"/> - <xsd:element name="faces-config-extension" - type="javaee:faces-config-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:choice> - <xsd:attribute name = "id" type = "xsd:ID"/> - <xsd:attribute name="version" - type="javaee:faces-config-versionType" - use="required"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for faces-config. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-applicationType"> - <xsd:annotation> - <xsd:documentation> - - The "application" element provides a mechanism to define the - various per-application-singleton implementation artifacts for - a particular web application that is utilizing - JavaServer Faces. For nested elements that are not specified, - the JSF implementation must provide a suitable default. - - </xsd:documentation> - </xsd:annotation> - - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:element name="action-listener" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "action-listener" element contains the fully - qualified class name of the concrete - ActionListener implementation class that will be - called during the Invoke Application phase of the - request processing lifecycle. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="default-render-kit-id" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "default-render-kit-id" element allows the - application to define a renderkit to be used other - than the standard one. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="message-bundle" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The base name of a resource bundle representing - the message resources for this application. See - the JavaDocs for the "java.util.ResourceBundle" - class for more information on the syntax of - resource bundle names. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="navigation-handler" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "navigation-handler" element contains the - fully qualified class name of the concrete - NavigationHandler implementation class that will - be called during the Invoke Application phase - of the request processing lifecycle, if the - default ActionListener (provided by the JSF - implementation) is used. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="view-handler" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "view-handler" element contains the fully - qualified class name of the concrete ViewHandler - implementation class that will be called during - the Restore View and Render Response phases of the - request processing lifecycle. The faces - implementation must provide a default - implementation of this class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="state-manager" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "state-manager" element contains the fully - qualified class name of the concrete StateManager - implementation class that will be called during - the Restore View and Render Response phases of the - request processing lifecycle. The faces - implementation must provide a default - implementation of this class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="el-resolver" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "el-resolver" element contains the fully - qualified class name of the concrete - javax.el.ELResolver implementation class - that will be used during the processing of - EL expressions. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="property-resolver" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "property-resolver" element contains the fully - qualified class name of the concrete - PropertyResolver implementation class that will - be used during the processing of value binding - expressions. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="variable-resolver" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "variable-resolver" element contains the fully - qualified class name of the concrete - VariableResolver implementation class that will - be used during the processing of value binding - expressions. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element - name="locale-config" - type="javaee:faces-config-locale-configType"/> - <xsd:element - name="resource-bundle" - type="javaee:faces-config-application-resource-bundleType"/> - <xsd:element name="application-extension" - type="javaee:faces-config-application-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:choice> - <xsd:attribute name = "id" type = "xsd:ID"/> - </xsd:complexType> - - <xsd:complexType name="faces-config-application-resource-bundleType"> - <xsd:annotation> - <xsd:documentation> - - The resource-bundle element inside the application element - references a java.util.ResourceBundle instance by name - using the var element. ResourceBundles referenced in this - manner may be returned by a call to - Application.getResourceBundle() passing the current - FacesContext for this request and the value of the var - element below. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="base-name" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The fully qualified class name of the - java.util.ResourceBundle instance. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="var" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The name by which this ResourceBundle instance - is retrieved by a call to - Application.getResourceBundle(). - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-application-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for application. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-factoryType"> - <xsd:annotation> - <xsd:documentation> - - The "factory" element provides a mechanism to define the - various Factories that comprise parts of the implementation - of JavaServer Faces. For nested elements that are not - specified, the JSF implementation must provide a suitable - default. - - </xsd:documentation> - </xsd:annotation> - - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:element name="application-factory" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "application-factory" element contains the - fully qualified class name of the concrete - ApplicationFactory implementation class that will - be called when - FactoryFinder.getFactory(APPLICATION_FACTORY) is - called. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="faces-context-factory" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "faces-context-factory" element contains the - fully qualified class name of the concrete - FacesContextFactory implementation class that will - be called when - FactoryFinder.getFactory(FACES_CONTEXT_FACTORY) - is called. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="lifecycle-factory" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "lifecycle-factory" element contains the fully - qualified class name of the concrete LifecycleFactory - implementation class that will be called when - FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="render-kit-factory" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "render-kit-factory" element contains the fully - qualified class name of the concrete RenderKitFactory - implementation class that will be called when - FactoryFinder.getFactory(RENDER_KIT_FACTORY) is - called. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="factory-extension" - type="javaee:faces-config-factory-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:choice> - <xsd:attribute name = "id" type = "xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-factory-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for factory. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-attributeType"> - <xsd:annotation> - <xsd:documentation> - - The "attribute" element represents a named, typed, value - associated with the parent UIComponent via the generic - attributes mechanism. - - Attribute names must be unique within the scope of the parent - (or related) component. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="attribute-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "attribute-name" element represents the name under - which the corresponding value will be stored, in the - generic attributes of the UIComponent we are related - to. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="attribute-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "attribute-class" element represents the Java type - of the value associated with this attribute name. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="default-value" - type="javaee:faces-config-default-valueType" - minOccurs="0"/> - <xsd:element name="suggested-value" - type="javaee:faces-config-suggested-valueType" - minOccurs="0"/> - <xsd:element name="attribute-extension" - type="javaee:faces-config-attribute-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name = "id" type = "xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-attribute-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for attribute. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-componentType"> - <xsd:annotation> - <xsd:documentation> - - The "component" element represents a concrete UIComponent - implementation class that should be registered under the - specified type identifier, along with its associated - properties and attributes. Component types must be unique - within the entire web application. - - Nested "attribute" elements identify generic attributes that - are recognized by the implementation logic of this component. - Nested "property" elements identify JavaBeans properties of - the component class that may be exposed for manipulation - via tools. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="component-type" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "component-type" element represents the name under - which the corresponding UIComponent class should be - registered. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="component-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "component-class" element represents the fully - qualified class name of a concrete UIComponent - implementation class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="facet" - type="javaee:faces-config-facetType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="attribute" - type="javaee:faces-config-attributeType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="property" - type="javaee:faces-config-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="component-extension" - type="javaee:faces-config-component-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-component-extensionType"> - <xsd:annotation> - <xsd:documentation> - Extension element for component. It may contain - implementation specific content. - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-default-localeType"> - <xsd:annotation> - <xsd:documentation> - - The "default-locale" element declares the default locale - for this application instance. - - It must be specified as :language:[_:country:[_:variant:]] - without the colons, for example "ja_JP_SJIS". The - separators between the segments may be '-' or '_'. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:extension base="javaee:faces-config-localeType"> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - - <xsd:complexType name="faces-config-default-valueType"> - <xsd:annotation> - <xsd:documentation> - - The "default-value" contains the value for the property or - attribute in which this element resides. This value differs - from the "suggested-value" in that the property or attribute - must take the value, whereas in "suggested-value" taking the - value is optional. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="faces-config-el-expressionType"> - <xsd:annotation> - <xsd:documentation> - - EL expressions present within a faces config file - must start with the character sequence of '#{' and - end with '}'. - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:string"> - <xsd:pattern value="#\{.*\}"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-facetType"> - <xsd:annotation> - <xsd:documentation> - - Define the name and other design-time information for a facet - that is associated with a renderer or a component. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="facet-name" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The "facet-name" element represents the facet name - under which a UIComponent will be added to its parent. - It must be of type "Identifier". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="facet-extension" - type="javaee:faces-config-facet-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-facet-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for facet. It may contain implementation - specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-from-view-idType"> - <xsd:annotation> - <xsd:documentation> - - The value of from-view-id must contain one of the following - values: - - - The exact match for a view identifier that is recognized - by the the ViewHandler implementation being used (such as - "/index.jsp" if you are using the default ViewHandler). - - - A proper prefix of a view identifier, plus a trailing - "*" character. This pattern indicates that all view - identifiers that match the portion of the pattern up to - the asterisk will match the surrounding rule. When more - than one match exists, the match with the longest pattern - is selected. - - - An "*" character, which means that this pattern applies - to all view identifiers. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-from-actionType"> - <xsd:annotation> - <xsd:documentation> - - The "from-action" element contains an action reference - expression that must have been executed (by the default - ActionListener for handling application level events) - in order to select the navigation rule. If not specified, - this rule will be relevant no matter which action reference - was executed (or if no action reference was executed). - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:extension base="javaee:faces-config-el-expressionType"> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-converterType"> - <xsd:annotation> - <xsd:documentation> - - The "converter" element represents a concrete Converter - implementation class that should be registered under the - specified converter identifier. Converter identifiers must - be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that - may be configured on the corresponding UIComponent in order - to affect the operation of the Converter. Nested "property" - elements identify JavaBeans properties of the Converter - implementation class that may be configured to affect the - operation of the Converter. "attribute" and "property" - elements are intended to allow component developers to - more completely describe their components to tools and users. - These elements have no required runtime semantics. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:choice> - <xsd:element name="converter-id" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "converter-id" element represents the - identifier under which the corresponding - Converter class should be registered. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="converter-for-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "converter-for-class" element represents the - fully qualified class name for which a Converter - class will be registered. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - - <xsd:element name="converter-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "converter-class" element represents the fully - qualified class name of a concrete Converter - implementation class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="attribute" - type="javaee:faces-config-attributeType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Nested "attribute" elements identify generic - attributes that may be configured on the - corresponding UIComponent in order to affect the - operation of the Converter. This attribute is - primarily for design-time tools and is not - specified to have any meaning at runtime. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="property" - type="javaee:faces-config-propertyType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Nested "property" elements identify JavaBeans - properties of the Converter implementation class - that may be configured to affect the operation of - the Converter. This attribute is primarily for - design-time tools and is not specified to have - any meaning at runtime. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="converter-extension" - type="javaee:faces-config-converter-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-converter-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for converter. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-lifecycleType"> - <xsd:annotation> - <xsd:documentation> - - The "lifecycle" element provides a mechanism to specify - modifications to the behaviour of the default Lifecycle - implementation for this web application. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="phase-listener" - type="javaee:fully-qualified-classType" - minOccurs="0" - maxOccurs="unbounded"> - - <xsd:annotation> - <xsd:documentation> - - The "phase-listener" element contains the fully - qualified class name of the concrete PhaseListener - implementation class that will be registered on - the Lifecycle. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="lifecycle-extension" - type="javaee:faces-config-lifecycle-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-lifecycle-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for lifecycle. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:simpleType name="faces-config-localeType"> - <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:complexType name="faces-config-locale-configType"> - <xsd:annotation> - <xsd:documentation> - - The "locale-config" element allows the app developer to - declare the supported locales for this application. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="default-locale" - type="javaee:faces-config-default-localeType" - minOccurs="0"> - </xsd:element> - <xsd:element name="supported-locale" - type="javaee:faces-config-supported-localeType" - minOccurs="0" - maxOccurs="unbounded"> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-managed-beanType"> - <xsd:annotation> - <xsd:documentation> - - The "managed-bean" element represents a JavaBean, of a - particular class, that will be dynamically instantiated - at runtime (by the default VariableResolver implementation) - if it is referenced as the first element of a value binding - expression, and no corresponding bean can be identified in - any scope. In addition to the creation of the managed bean, - and the optional storing of it into the specified scope, - the nested managed-property elements can be used to - initialize the contents of settable JavaBeans properties of - the created instance. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="managed-bean-name" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The "managed-bean-name" element represents the - attribute name under which a managed bean will - be searched for, as well as stored (unless the - "managed-bean-scope" value is "none"). - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="managed-bean-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "managed-bean-class" element represents the fully - qualified class name of the Java class that will be - used`to instantiate a new instance if creation of the - specified`managed bean is requested. - - The specified class must conform to standard JavaBeans - conventions. In particular, it must have a public - zero-arguments constructor, and zero or more public - property setters. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element - name="managed-bean-scope" - type="javaee:faces-config-managed-bean-scopeOrNoneType"> - <xsd:annotation> - <xsd:documentation> - - The "managed-bean-scope" element represents the scope - into which a newly created instance of the specified - managed bean will be stored (unless the value is - "none"). - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:choice> - <xsd:element name="managed-property" - type="javaee:faces-config-managed-propertyType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="map-entries" - type="javaee:faces-config-map-entriesType"/> - <xsd:element name="list-entries" - type="javaee:faces-config-list-entriesType"/> - </xsd:choice> - <xsd:element name="managed-bean-extension" - type="javaee:faces-config-managed-bean-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-managed-bean-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for managed-bean. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-managed-bean-scopeOrNoneType"> - <xsd:annotation> - <xsd:documentation> - - <![CDATA[ - Defines the legal values for the <managed-bean-scope> - element's body content, which includes all of the scopes - normally used in a web application, plus the "none" value - indicating that a created bean should not be stored into - any scope. - ]]> - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="request"/> - <xsd:enumeration value="session"/> - <xsd:enumeration value="application"/> - <xsd:enumeration value="none"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-managed-propertyType"> - <xsd:annotation> - <xsd:documentation> - - The "managed-property" element represents an individual - property of a managed bean that will be configured to the - specified value (or value set) if the corresponding - managed bean is automatically created. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="property-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "property-name" element represents the JavaBeans - property name under which the corresponding value may - be stored. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="property-class" - type="javaee:java-typeType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The "property-class" element represents the Java type - of the value associated with this property name. - If not specified, it can be inferred from existing - classes; however, this element should be specified - if the configuration file is going to be the source - for generating the corresponding classes. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:choice> - <xsd:element name="map-entries" - type="javaee:faces-config-map-entriesType"/> - <xsd:element name="null-value" - type="javaee:faces-config-null-valueType"> - </xsd:element> - <xsd:element name="value" - type="javaee:faces-config-valueType"/> - <xsd:element name="list-entries" - type="javaee:faces-config-list-entriesType"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-map-entryType"> - <xsd:annotation> - <xsd:documentation> - - The "map-entry" element reprsents a single key-entry pair - that will be added to the computed value of a managed - property of type java.util.Map. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="key" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "key" element is the String representation of a - map key that will be stored in a managed property of - type java.util.Map. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:choice> - <xsd:element name="null-value" - type="javaee:faces-config-null-valueType"/> - <xsd:element name="value" - type="javaee:faces-config-valueType"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-map-entriesType"> - <xsd:annotation> - <xsd:documentation> - - The "map-entries' element represents a set of key-entry pairs - that will be added to the computed value of a managed property - of type java.util.Map. In addition, the Java class types - of the key and entry values may be optionally declared. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="key-class" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The "key-class" element defines the Java type to which - each "key" element in a set of "map-entry" elements - will be converted to. If omitted, "java.lang.String" - is assumed. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="value-class" - type="javaee:faces-config-value-classType" - minOccurs="0"/> - <xsd:element name="map-entry" - type="javaee:faces-config-map-entryType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-navigation-caseType"> - <xsd:annotation> - <xsd:documentation> - - The "navigation-case" element describes a particular - combination of conditions that must match for this case to - be executed, and the view id of the component tree that - should be selected next. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="from-action" - type="javaee:faces-config-from-actionType" - minOccurs="0"> - </xsd:element> - <xsd:element name="from-outcome" - type="javaee:string" minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The "from-outcome" element contains a logical outcome - string returned by the execution of an application - action method selected via an "actionRef" property - (or a literal value specified by an "action" property) - of a UICommand component. If specified, this rule - will be relevant only if the outcome value matches - this element's value. If not specified, this rule - will be relevant no matter what the outcome value was. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="to-view-id" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "to-view-id" element contains the view identifier - of the next view that should be displayed if this - navigation rule is matched. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element - name="redirect" - type="javaee:faces-config-redirectType" minOccurs="0"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-navigation-ruleType"> - <xsd:annotation> - <xsd:documentation> - - The "navigation-rule" element represents an individual - decision rule that will be utilized by the default - NavigationHandler implementation to make decisions on - what view should be displayed next, based on the - view id being processed. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="from-view-id" - type="javaee:faces-config-from-view-idType" - minOccurs="0"/> - <xsd:element name="navigation-case" - type="javaee:faces-config-navigation-caseType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element - name="navigation-rule-extension" - type="javaee:faces-config-navigation-rule-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-navigation-rule-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for navigation-rule. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-null-valueType"> - <xsd:annotation> - <xsd:documentation> - - The "null-value" element indicates that the managed - property in which we are nested will be explicitly - set to null if our managed bean is automatically - created. This is different from omitting the managed - property element entirely, which will cause no - property setter to be called for this property. - - The "null-value" element can only be used when the - associated "property-class" identifies a Java class, - not a Java primitive. - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-propertyType"> - <xsd:annotation> - <xsd:documentation> - - The "property" element represents a JavaBean property of the - Java class represented by our parent element. - - Property names must be unique within the scope of the Java - class that is represented by the parent element, and must - correspond to property names that will be recognized when - performing introspection against that class via - java.beans.Introspector. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="property-name" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "property-name" element represents the JavaBeans - property name under which the corresponding value - may be stored. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="property-class" - type="javaee:java-typeType"> - <xsd:annotation> - <xsd:documentation> - - The "property-class" element represents the Java type - of the value associated with this property name. - If not specified, it can be inferred from existing - classes; however, this element should be specified if - the configuration file is going to be the source for - generating the corresponding classes. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="default-value" - type="javaee:faces-config-default-valueType" - minOccurs="0"/> - <xsd:element name="suggested-value" - type="javaee:faces-config-suggested-valueType" - minOccurs="0"/> - <xsd:element name="property-extension" - type="javaee:faces-config-property-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-property-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for property. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-redirectType"> - <xsd:annotation> - <xsd:documentation> - - The "redirect" element indicates that navigation to the - specified "to-view-id" should be accomplished by - performing an HTTP redirect rather than the usual - ViewHandler mechanisms. - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-referenced-beanType"> - <xsd:annotation> - <xsd:documentation> - - The "referenced-bean" element represents at design time the - promise that a Java object of the specified type will exist at - runtime in some scope, under the specified key. This can be - used by design time tools to construct user interface dialogs - based on the properties of the specified class. The presence - or absence of a referenced bean element has no impact on the - JavaServer Faces runtime environment inside a web application. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="referenced-bean-name" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The "referenced-bean-name" element represents the - attribute name under which the corresponding - referenced bean may be assumed to be stored, in one - of 'request', 'session', or 'application' scopes. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="referenced-bean-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "referenced-bean-class" element represents the - fully qualified class name of the Java class - (either abstract or concrete) or Java interface - implemented by the corresponding referenced bean. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-render-kitType"> - <xsd:annotation> - <xsd:documentation> - - The "render-kit" element represents a concrete RenderKit - implementation that should be registered under the specified - render-kit-id. If no render-kit-id is specified, the - identifier of the default RenderKit - (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="render-kit-id" - type="javaee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The "render-kit-id" element represents an identifier - for the RenderKit represented by the parent - "render-kit" element. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="render-kit-class" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The "render-kit-class" element represents the fully - qualified class name of a concrete RenderKit - implementation class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="renderer" - type="javaee:faces-config-rendererType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="render-kit-extension" - type="javaee:faces-config-render-kit-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-rendererType"> - <xsd:annotation> - <xsd:documentation> - - The "renderer" element represents a concrete Renderer - implementation class that should be registered under the - specified component family and renderer type identifiers, - in the RenderKit associated with the parent "render-kit" - element. Combinations of component family and - renderer type must be unique within the RenderKit - associated with the parent "render-kit" element. - - Nested "attribute" elements identify generic component - attributes that are recognized by this renderer. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="component-family" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "component-family" element represents the - component family for which the Renderer represented - by the parent "renderer" element will be used. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="renderer-type" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "renderer-type" element represents a renderer type - identifier for the Renderer represented by the parent - "renderer" element. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="renderer-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "renderer-class" element represents the fully - qualified class name of a concrete Renderer - implementation class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="facet" - type="javaee:faces-config-facetType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="attribute" - type="javaee:faces-config-attributeType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="renderer-extension" - type="javaee:faces-config-renderer-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-renderer-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for renderer. It may contain implementation - specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-render-kit-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for render-kit. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-suggested-valueType"> - <xsd:annotation> - <xsd:documentation> - - The "suggested-value" contains the value for the property or - attribute in which this element resides. This value is - advisory only and is intended for tools to use when - populating pallettes. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:string"/> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-supported-localeType"> - <xsd:annotation> - <xsd:documentation> - - The "supported-locale" element allows authors to declare - which locales are supported in this application instance. - - It must be specified as :language:[_:country:[_:variant:]] - without the colons, for example "ja_JP_SJIS". The - separators between the segments may be '-' or '_'. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:extension base="javaee:faces-config-localeType"> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:extension> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-validatorType"> - <xsd:annotation> - <xsd:documentation> - - The "validator" element represents a concrete Validator - implementation class that should be registered under the - specified validator identifier. Validator identifiers must - be unique within the entire web application. - - Nested "attribute" elements identify generic attributes that - may be configured on the corresponding UIComponent in order - to affect the operation of the Validator. Nested "property" - elements identify JavaBeans properties of the Validator - implementation class that may be configured to affect the - operation of the Validator. "attribute" and "property" - elements are intended to allow component developers to - more completely describe their components to tools and users. - These elements have no required runtime semantics. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="validator-id" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - The "validator-id" element represents the identifier - under which the corresponding Validator class should - be registered. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="validator-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - The "validator-class" element represents the fully - qualified class name of a concrete Validator - implementation class. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="attribute" - type="javaee:faces-config-attributeType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Nested "attribute" elements identify generic - attributes that may be configured on the - corresponding UIComponent in order to affect the - operation of the Validator. This attribute is - primarily for design-time tools and is not - specified to have any meaning at runtime. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="property" - type="javaee:faces-config-propertyType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Nested "property" elements identify JavaBeans - properties of the Validator implementation class - that may be configured to affect the operation of - the Validator. This attribute is primarily for - design-time tools and is not specified to have - any meaning at runtime. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="validator-extension" - type="javaee:faces-config-validator-extensionType" - minOccurs="0" - maxOccurs="unbounded"/> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name = "faces-config-validator-extensionType"> - <xsd:annotation> - <xsd:documentation> - - Extension element for validator. It may contain - implementation specific content. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:any namespace="##any" - processContents="lax" - minOccurs="0" - maxOccurs="unbounded" /> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="faces-config-valueType"> - <xsd:annotation> - <xsd:documentation> - - The "value" element is the String representation of - a literal value to which a scalar managed property - will be set, or a value binding expression ("#{...}") - that will be used to calculate the required value. - It will be converted as specified for the actual - property type. - - </xsd:documentation> - </xsd:annotation> - <xsd:union - memberTypes="javaee:faces-config-el-expressionType xsd:string"/> - </xsd:simpleType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-value-classType"> - <xsd:annotation> - <xsd:documentation> - - The "value-class" element defines the Java type to which each - "value" element's value will be converted to, prior to adding - it to the "list-entries" list for a managed property that is - a java.util.List, or a "map-entries" map for a managed - property that is a java.util.Map. - - </xsd:documentation> - </xsd:annotation> - <xsd:simpleContent> - <xsd:restriction base="javaee:fully-qualified-classType"/> - </xsd:simpleContent> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:complexType name="faces-config-list-entriesType"> - <xsd:annotation> - <xsd:documentation> - - The "list-entries" element represents a set of initialization - elements for a managed property that is a java.util.List or an - array. In the former case, the "value-class" element can - optionally be used to declare the Java type to which each - value should be converted before adding it to the Collection. - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="value-class" - type="javaee:faces-config-value-classType" - minOccurs="0"/> - <xsd:choice minOccurs="0" maxOccurs="unbounded"> - <xsd:element name="null-value" - type="javaee:faces-config-null-valueType"/> - <xsd:element name="value" - type="javaee:faces-config-valueType"/> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - - <!-- **************************************************** --> - - <xsd:simpleType name="faces-config-versionType"> - <xsd:annotation> - <xsd:documentation> - - This type contains the recognized versions of - faces-config supported. - - </xsd:documentation> - </xsd:annotation> - <xsd:restriction base="xsd:token"> - <xsd:enumeration value="1.2"/> - </xsd:restriction> - </xsd:simpleType> - - <!-- **************************************************** --> - -</xsd:schema> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_1.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_1.dtd deleted file mode 100644 index 25c8e87396..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_1.dtd +++ /dev/null @@ -1,265 +0,0 @@ -<!-- -Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road, -Palo Alto, CA 94303, U.S.A. All rights reserved. - -This product or document is protected by copyright and distributed -under licenses restricting its use, copying, distribution, and -decompilation. No part of this product or documentation 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, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans, -are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S. -and other countries. - -All SPARC trademarks are used under license and are trademarks -or registered trademarks of SPARC International, Inc. -in the U.S. and other countries. Products bearing SPARC -trademarks are based upon an architecture developed by Sun Microsystems, Inc. - -PostScript is a registered trademark of Adobe Systems, Inc. - - -Federal Acquisitions: Commercial Software - Government Users Subject to -Standard License Terms and Conditions. - - - -DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED -CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY -IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT -TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY -INVALID. - -_________________________________________________________________________ -Copyright 1999 Sun Microsystems, Inc., -901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis. -Tous droits re'serve's. - - -Ce produit ou document est prote'ge' par un copyright et distribue' avec -des licences qui en restreignent l'utilisation, la copie, la distribution, -et la de'compilation. Aucune partie de ce produit ou de sa documentation -associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen -que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses -bailleurs de licence, s'il y en a. - -Le logiciel de'tenu par des tiers, et qui comprend la technologie -relative aux polices de caracte`res, est prote'ge' par un copyright -et licencie' par des fournisseurs de Sun. - -Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java -Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans, -sont des marques de fabrique ou des marques de'pose'es de Sun -Microsystems, Inc. aux Etats-Unis et dans d'autres pays. - -Toutes les marques SPARC sont utilise'es sous licence et sont -des marques de fabrique ou des marques de'pose'es de SPARC -International, Inc. aux Etats-Unis et dans -d'autres pays. Les produits portant les marques SPARC sont -base's sur une architecture de'veloppe'e par Sun Microsystems, Inc. - -Postcript est une marque enregistre'e d'Adobe Systems Inc. - -LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, -DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, -DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT -TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE -A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. ---> - -<!-- - - This is the DTD defining the JavaServer Pages 1.1 Tag Library - descriptor (.tld) (XML) file format/syntax. - - A Tag Library is a JAR file containing a valid instance of a Tag Library - Descriptor (taglib.tld) file in the META-INF subdirectory, along with the - appropriate implementing classes, and other resources required to - implement the tags defined therein. - - --> - -<!-- -The taglib tag is the document root, it defines: - -tlibversion the version of the tag library implementation -jspversion the version of JSP the tag library depends upon - -shortname a simple default short name that could be used by - a JSP authoring tool to create names with a mnemonic - value; for example, the it may be used as the prefered - prefix value in taglib directives -uri a uri uniquely identifying this taglib -info a simple string describing the "use" of this taglib, - should be user discernable ---> - -<!ELEMENT taglib (tlibversion, jspversion?, shortname, uri?, info?, tag+) > -<!ATTLIST taglib id ID #IMPLIED - xmlns CDATA #FIXED - "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd" -> - -<!-- -Describes this version (number) of the taglibrary (dewey decimal) - -#PCDATA ::= [0-9]*{ "."[0-9] }0..3 ---> - -<!ELEMENT tlibversion (#PCDATA) > - -<!-- -Describes the JSP version (number) this taglibrary requires in -order to function (dewey decimal) - -The default is 1.1 - -#PCDATA ::= [0-9]*{ "."[0-9] }0..3 ---> - -<!ELEMENT jspversion (#PCDATA) > - -<!-- -Defines a short (default) shortname to be used for tags and -variable names used/created by this tag library. Do not use -white space, and do not start with digits or underscore. - -#PCDATA ::= NMTOKEN ---> - -<!ELEMENT shortname (#PCDATA) > - -<!-- -Defines a public URI that uniquely identifies this version of -the taglibrary Leave it empty if it does not apply. ---> - -<!ELEMENT uri (#PCDATA) > - -<!-- -Defines an arbitrary text string descirbing the tag library ---> - -<!ELEMENT info (#PCDATA) > - -<!-- -The tag defines a unique tag in this tag library, defining: - -- the unique tag/element name -- the subclass of javax.servlet.jsp.tagext.Tag implementation class -- an optional subclass of javax.servlet.jsp.tagext.TagExtraInfo -- the body content type (hint) -- optional tag-specific information -- any attributes ---> - -<!ELEMENT tag (name, tagclass, teiclass?, bodycontent?, info?, attribute*) > - -<!-- -Defines the subclass of javax.serlvet.jsp.tagext.Tag that implements -the request time semantics for this tag. (required) - -#PCDATA ::= fully qualified Java class name ---> - -<!ELEMENT tagclass (#PCDATA) > - -<!-- -Defines the subclass of javax.servlet.jsp.tagext.TagExtraInfo for -this tag. (optional) - -If this is not given, the class is not consulted at translation time. - -#PCDATA ::= fully qualified Java class name ---> - -<!ELEMENT teiclass (#PCDATA) > - -<!-- -Provides a hint as to the content of the body of this tag. Primarily -intended for use by page composition tools. - -There are currently three values specified: - -tagdependent The body of the tag is interpreted by the tag - implementation itself, and is most likely in a - different "langage", e.g embedded SQL statements. - -JSP The body of the tag contains nested JSP syntax - -empty The body must be empty - -The default (if not defined) is JSP - -#PCDATA ::= tagdependent | JSP | empty - ---> - -<!ELEMENT bodycontent (#PCDATA) > - -<!-- -The attribute tag defines an attribute for the nesting tag - -An attribute definition is composed of: - -- the attributes name (required) -- if the attribute is required or optional (optional) -- if the attributes value may be dynamically calculated at runtime - by a scriptlet expression (optional) - ---> - -<!ELEMENT attribute (name, required? , rtexprvalue?) > - -<!-- -Defines the canonical name of a tag or attribute being defined - -#PCDATA ::= NMTOKEN ---> - -<!ELEMENT name (#PCDATA) > - -<!-- -Defines if the nesting attribute is required or optional. - -#PCDATA ::= true | false | yes | no - -If not present then the default is "false", i.e the attribute -is optional. ---> - -<!ELEMENT required (#PCDATA) > - -<!-- -Defines if the nesting attribute can have scriptlet expressions as -a value, i.e the value of the attribute may be dynamically calculated -at request time, as opposed to a static value determined at translation -time. - -#PCDATA ::= true | false | yes | no - -If not present then the default is "false", i.e the attribute -has a static value ---> - -<!ELEMENT rtexprvalue (#PCDATA) > - -<!ATTLIST tlibversion id ID #IMPLIED> -<!ATTLIST jspversion id ID #IMPLIED> -<!ATTLIST shortname id ID #IMPLIED> -<!ATTLIST uri id ID #IMPLIED> -<!ATTLIST info id ID #IMPLIED> -<!ATTLIST tag id ID #IMPLIED> -<!ATTLIST tagclass id ID #IMPLIED> -<!ATTLIST teiclass id ID #IMPLIED> -<!ATTLIST bodycontent id ID #IMPLIED> -<!ATTLIST attribute id ID #IMPLIED> -<!ATTLIST name id ID #IMPLIED> -<!ATTLIST required id ID #IMPLIED> -<!ATTLIST rtexprvalue id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_2.dtd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_2.dtd deleted file mode 100644 index 602eb5c98e..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_1_2.dtd +++ /dev/null @@ -1,468 +0,0 @@ - -<!-- - Copyright 2002 Sun Microsystems, Inc. All rights reserved. - Use is subject to license terms. - --> - -<!-- - - This is the DTD defining the JavaServer Pages 1.2 Tag Library - descriptor (.tld) (XML) file format/syntax. - - A Tag Library is a JAR file containing a valid instance of a Tag Library - Descriptor (taglib.tld) file in the META-INF subdirectory, along with the - appropriate implementing classes, and other resources required to - implement the tags defined therein. - - Use is subject to license terms. - --> - -<!NOTATION WEB-JSPTAGLIB.1_2 PUBLIC - "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"> - -<!-- -This is the XML DTD for the JSP 1.2 Tag Library Descriptor. -All JSP 1.2 tag library descriptors must include a DOCTYPE -of the following form: - - <!DOCTYPE taglib - PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN" - "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd"> - ---> - -<!-- -The taglib tag is the document root, it defines: - -tlib-version the version of the tag library implementation - -jsp-version the version of JSP the tag library depends upon - -short-name a simple default short name that could be used by - a JSP authoring tool to create names with a mnemonic - value; for example, the it may be used as the prefered - prefix value in taglib directives - -uri a uri uniquely identifying this taglib - -display-name the display-name element contains a short name that - is intended to be displayed by tools -small-icon optional small-icon that can be used by tools - -large-icon optional large-icon that can be used by tools - -description a simple string describing the "use" of this taglib, - should be user discernable - -validator optional TagLibraryValidator information - -listener optional event listener specification - - ---> - -<!ELEMENT taglib (tlib-version, jsp-version, short-name, uri?, - display-name?, small-icon?, large-icon?, description?, - validator?, listener*, tag+) > - -<!ATTLIST taglib id ID #IMPLIED - xmlns CDATA #FIXED - "http://java.sun.com/JSP/TagLibraryDescriptor" -> - -<!-- -Describes this version (number) of the taglibrary (dewey decimal) - -#PCDATA ::= [0-9]*{ "."[0-9] }0..3 ---> - -<!ELEMENT tlib-version (#PCDATA) > - -<!-- -Describes the JSP version (number) this taglibrary requires in -order to function (dewey decimal) - -The default is 1.2 - -#PCDATA ::= [0-9]*{ "."[0-9] }0..3 ---> - -<!ELEMENT jsp-version (#PCDATA) > - -<!-- -Defines a short (default) short-name to be used for tags and -variable names used/created by this tag library. Do not use -white space, and do not start with digits or underscore. - -#PCDATA ::= NMTOKEN ---> - -<!ELEMENT short-name (#PCDATA) > - -<!-- -Defines a public URI that uniquely identifies this version of -the taglibrary. Leave it empty if it does not apply. ---> - -<!ELEMENT uri (#PCDATA) > - -<!-- -Defines an arbitrary text string descirbing the tag library ---> - -<!ELEMENT description (#PCDATA) > - -<!-- - -Defines an optional validator that can be used to -validate the conformance of a JSP page to using this tag library. ---> - -<!ELEMENT validator (validator-class, init-param*, description?) > - - -<!-- - -Defines the TagLibraryValidator class that can be used to -validate the conformance of a JSP page to using this tag library. ---> - -<!ELEMENT validator-class (#PCDATA) > - - -<!-- - -The init-param element contains a name/value pair as an -initialization param ---> - -<!ELEMENT init-param (param-name, param-value, description?)> - -<!-- - -The param-name element contains the name of a parameter. ---> - -<!ELEMENT param-name (#PCDATA)> - -<!-- - -The param-value element contains the value of a parameter. ---> - -<!ELEMENT param-value (#PCDATA)> - - -<!-- - -Defines an optional event listener object to be instantiated and -registered automatically. ---> - -<!ELEMENT listener (listener-class) > - -<!-- - -The listener-class element declares a class in the application that -must be registered as a web application listener bean. See the -Servlet 2.3 specification for details. ---> - -<!ELEMENT listener-class (#PCDATA) > - - -<!-- -The tag defines a unique tag in this tag library. It has one -attribute, id. - -The tag element may have several subelements defining: - -name The unique action name - -tag-class The tag handler class implementing - javax.servlet.jsp.tagext.Tag - -tei-class An optional subclass of - javax.servlet.jsp.tagext.TagExtraInfo - -body-content The body content type - -display-name A short name that is intended to be displayed - by tools - -small-icon Optional small-icon that can be used by tools - -large-icon Optional large-icon that can be used by tools - -description Optional tag-specific information - -variable Optional scripting variable information - -attribute All attributes of this action - -example Optional informal description of an example of a - use of this tag - ---> - -<!ELEMENT tag (name, tag-class, tei-class?, body-content?, display-name?, - small-icon?, large-icon?, description?, variable*, attribute*, - example?) > - -<!-- -Defines the subclass of javax.serlvet.jsp.tagext.Tag that implements -the request time semantics for this tag. (required) - -#PCDATA ::= fully qualified Java class name ---> - -<!ELEMENT tag-class (#PCDATA) > - -<!-- -Defines the subclass of javax.servlet.jsp.tagext.TagExtraInfo for -this tag. (optional) - -If this is not given, the class is not consulted at translation time. - -#PCDATA ::= fully qualified Java class name ---> - -<!ELEMENT tei-class (#PCDATA) > - -<!-- -Provides a hint as to the content of the body of this tag. Primarily -intended for use by page composition tools. - -There are currently three values specified: - -tagdependent The body of the tag is interpreted by the tag - implementation itself, and is most likely in a - different "langage", e.g embedded SQL statements. - -JSP The body of the tag contains nested JSP syntax - -empty The body must be empty - -The default (if not defined) is JSP - -#PCDATA ::= tagdependent | JSP | empty - ---> - -<!ELEMENT body-content (#PCDATA) > - -<!-- - -The display-name element contains a short name that is intended -to be displayed by tools. ---> - -<!ELEMENT display-name (#PCDATA) > - - -<!-- - -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 -tag library. The image must be either in the JPEG or GIF format, and -the file name must end with the suffix ".jpg" or ".gif" respectively. -The icon can be used by tools. ---> - -<!ELEMENT large-icon (#PCDATA) > - -<!-- - -The small-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 -tag library. The image must be either in the JPEG or GIF format, and -the file name must end with the suffix ".jpg" or ".gif" respectively. -The icon can be used by tools. ---> - -<!ELEMENT small-icon (#PCDATA) > - -<!-- - -The example element contains an informal description of an example -of the use of a tag. ---> - -<!ELEMENT example (#PCDATA) > - -<!-- - -The variable tag provides information on the scripting variables -defined by this tag. It is a (translation time) error for a tag -that has one or more variable subelements to have a TagExtraInfo -class that returns a non-null object. - -The subelements of variable are of the form: - -name-given The variable name as a constant - -name-from-attribute The name of an attribute whose (translation - time) value will give the name of the - variable. One of name-given or - name-from-attribute is required. - -variable-class Name of the class of the variable. - java.lang.String is default. - -declare Whether the variable is declared or not. - True is the default. - -scope The scope of the scripting varaible - defined. NESTED is default. - -description Optional description of this variable - ---> - -<!ELEMENT variable ( (name-given | name-from-attribute), variable-class?, - declare?, scope?, description?) > - -<!-- - -The name for the scripting variable. One of name-given or -name-from-attribute is required. ---> - -<!ELEMENT name-given (#PCDATA) > - -<!-- - -The name of an attribute whose (translation-time) value will give -the name of the variable. One of name-given or name-from-attribute -is required. ---> - -<!ELEMENT name-from-attribute (#PCDATA) > - -<!-- - -The optional name of the class for the scripting variable. The -default is java.lang.String. ---> - -<!ELEMENT variable-class (#PCDATA) > - -<!-- - -Whether the scripting variable is to be defined or not. See -TagExtraInfo for details. This element is optional and "true" -is the default. ---> - -<!ELEMENT declare (#PCDATA) > - -<!-- - -The scope of the scripting variable. See TagExtraInfo for details. -The element is optional and "NESTED" is the default. Other legal -values are "AT_BEGIN" and "AT_END". ---> - -<!ELEMENT scope (#PCDATA) > - -<!-- - -The attribute tag defines an attribute for the nesting tag - -An attribute definition is composed of: - -- the attributes name (required) -- if the attribute is required or optional (optional) -- if the attributes value may be dynamically calculated at runtime - by a scriptlet expression (optional) -- the type of the attributes value (optional) -- an informal description of the meaning of the attribute (optional) - ---> - - -<!-- -The attribute tag defines an attribute for the nesting tag - -An attribute definition is composed of: - -- the attributes name (required) - -- if the attribute is required or optional (optional) - -- if the attributes value may be dynamically calculated at runtime - by a scriptlet expression (optional) - -- the type of the attributes value (optional) - -- an informal description of the meaning of the attribute (optional) ---> - -<!ELEMENT attribute (name, required? , rtexprvalue?, type?, description?) > - -<!-- -Defines the canonical name of a tag or attribute being defined - -#PCDATA ::= NMTOKEN ---> - -<!ELEMENT name (#PCDATA) > - -<!-- -Defines if the nesting attribute is required or optional. - -#PCDATA ::= true | false | yes | no - -If not present then the default is "false", i.e the attribute -is optional. ---> - -<!ELEMENT required (#PCDATA) > - -<!-- -Defines if the nesting attribute can have scriptlet expressions as -a value, i.e the value of the attribute may be dynamically calculated -at request time, as opposed to a static value determined at translation -time. - -#PCDATA ::= true | false | yes | no - -If not present then the default is "false", i.e the attribute -has a static value ---> - -<!ELEMENT rtexprvalue (#PCDATA) > - - -<!-- - -Defines the Java type of the attributes value. For static values -(those determined at translation time) the type is always -java.lang.String. ---> - -<!ELEMENT type (#PCDATA) > - - -<!-- ID attributes --> - -<!ATTLIST tlib-version id ID #IMPLIED> -<!ATTLIST jsp-version id ID #IMPLIED> -<!ATTLIST short-name id ID #IMPLIED> -<!ATTLIST uri id ID #IMPLIED> -<!ATTLIST description id ID #IMPLIED> -<!ATTLIST example id ID #IMPLIED> -<!ATTLIST tag id ID #IMPLIED> -<!ATTLIST tag-class id ID #IMPLIED> -<!ATTLIST tei-class id ID #IMPLIED> -<!ATTLIST body-content id ID #IMPLIED> -<!ATTLIST attribute id ID #IMPLIED> -<!ATTLIST name id ID #IMPLIED> -<!ATTLIST required id ID #IMPLIED> -<!ATTLIST rtexprvalue id ID #IMPLIED> - - -<!ATTLIST param-name id ID #IMPLIED> -<!ATTLIST param-value id ID #IMPLIED> -<!ATTLIST listener id ID #IMPLIED> -<!ATTLIST listener-class id ID #IMPLIED> diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_0.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_0.xsd deleted file mode 100644 index eb5864190f..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_0.xsd +++ /dev/null @@ -1,1010 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xsd:schema - targetNamespace="http://java.sun.com/xml/ns/j2ee" - xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" - xmlns:xsd="http://www.w3.org/2001/XMLSchema" - xmlns:xml="http://www.w3.org/XML/1998/namespace" - elementFormDefault="qualified" - attributeFormDefault="unqualified" - version="2.0"> - - <xsd:annotation> - <xsd:documentation> - @(#)web-jsptaglibrary_2_0.xsds 1.36 08/18/03 - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - - Copyright 2003 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. - - </xsd:documentation> - </xsd:annotation> - - <xsd:annotation> - <xsd:documentation> - <![CDATA[ - - This is the XML Schema for the JSP Taglibrary - descriptor. All Taglibrary descriptors must - indicate the tag library schema by using the Taglibrary - namespace: - - http://java.sun.com/xml/ns/j2ee - - and by indicating the version of the schema by - using the version element as shown below: - - <taglib xmlns="http://java.sun.com/xml/ns/j2ee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="..." - version="2.0"> - ... - </taglib> - - The instance documents may indicate the published - version of the schema using xsi:schemaLocation attribute - for J2EE namespace with the following location: - - http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="j2ee_1_4.xsd"/> - - -<!-- **************************************************** --> - - - <xsd:element name="taglib" type="j2ee:tldTaglibType"> - <xsd:annotation> - <xsd:documentation> - - The taglib tag is the document root. - The definition of taglib is provided - by the tldTaglibType. - - </xsd:documentation> - </xsd:annotation> - <xsd:unique name="tag-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The taglib element contains, among other things, tag and - tag-file elements. - The name subelements of these elements must each be unique. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:tag|j2ee:tag-file"/> - <xsd:field xpath="j2ee:name"/> - </xsd:unique> - - <xsd:unique name="function-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The taglib element contains function elements. - The name subelements of these elements must each be unique. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="j2ee:function"/> - <xsd:field xpath="j2ee:name"/> - </xsd:unique> - - </xsd:element> - - -<!-- **************************************************** --> - - <xsd:complexType name="body-contentType"> - <xsd:annotation> - <xsd:documentation> - - Specifies the type of body that is valid for a tag. - This value is used by the JSP container to validate - that a tag invocation has the correct body syntax and - by page composition tools to assist the page author - in providing a valid tag body. - - There are currently four values specified: - - tagdependent The body of the tag is interpreted by the tag - implementation itself, and is most likely - in a different "language", e.g embedded SQL - statements. - - JSP The body of the tag contains nested JSP - syntax. - - empty The body must be empty - - scriptless The body accepts only template text, EL - Expressions, and JSP action elements. No - scripting elements are allowed. - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="tagdependent"/> - <xsd:enumeration value="JSP"/> - <xsd:enumeration value="empty"/> - <xsd:enumeration value="scriptless"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="extensibleType" abstract="true"> - <xsd:annotation> - <xsd:documentation> - - The extensibleType is an abstract base type that is used to - define the type of extension-elements. Instance documents - must substitute a known type to define the extension by - using xsi:type attribute to define the actual type of - extension-elements. - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="functionType"> - <xsd:annotation> - <xsd:documentation> - - The function element is used to provide information on each - function in the tag library that is to be exposed to the EL. - - The function element may have several subelements defining: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name A unique name for this function - - function-class Provides the name of the Java class that - implements the function - - function-signature Provides the signature, as in the Java - Language Specification, of the Java - method that is to be used to implement - the function. - - example Optional informal description of an - example of a use of this function - - function-extension Zero or more extensions that provide extra - information about this function, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="name" - type="j2ee:tld-canonical-nameType"> - <xsd:annotation> - <xsd:documentation> - - A unique name for this function. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="function-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Provides the fully-qualified class name of the Java - class containing the static method that implements - the function. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="function-signature" - type="j2ee:string"> - <xsd:annotation> - <xsd:documentation> - - Provides the signature, of the static Java method that is - to be used to implement the function. The syntax of the - function-signature element is as follows: - - FunctionSignature ::= ReturnType S MethodName S? - '(' S? Parameters? S? ')' - - ReturnType ::= Type - - MethodName ::= Identifier - - Parameters ::= Parameter - | ( Parameter S? ',' S? Parameters ) - - Parameter ::= Type - - Where: - - * Type is a basic type or a fully qualified Java class name - (including package name), as per the 'Type' production - in the Java Language Specification, Second Edition, - Chapter 18. - - * Identifier is a Java identifier, as per the 'Identifier' - production in the Java Language Specification, Second - Edition, Chapter 18. - - Example: - - java.lang.String nickName( java.lang.String, int ) - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="example" - type="j2ee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of this function. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="function-extension" - type="j2ee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Function extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tagFileType"> - <xsd:annotation> - <xsd:documentation> - - Defines an action in this tag library that is implemented - as a .tag file. - - The tag-file element has two required subelements: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name The unique action name - - path Where to find the .tag file implementing this - action, relative to the root of the web - application or the root of the JAR file for a - tag library packaged in a JAR. This must - begin with /WEB-INF/tags if the .tag file - resides in the WAR, or /META-INF/tags if the - .tag file resides in a JAR. - - example Optional informal description of an - example of a use of this tag - - tag-extension Zero or more extensions that provide extra - information about this tag, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="name" - type="j2ee:tld-canonical-nameType"/> - <xsd:element name="path" - type="j2ee:pathType"/> - <xsd:element name="example" - type="j2ee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of a tag. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tag-extension" - type="j2ee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Tag extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tagType"> - <xsd:annotation> - <xsd:documentation> - - The tag defines a unique tag in this tag library. It has one - attribute, id. - - The tag element may have several subelements defining: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name The unique action name - - tag-class The tag handler class implementing - javax.servlet.jsp.tagext.JspTag - - tei-class An optional subclass of - javax.servlet.jsp.tagext.TagExtraInfo - - body-content The body content type - - variable Optional scripting variable information - - attribute All attributes of this action that are - evaluated prior to invocation. - - dynamic-attributes Whether this tag supports additional - attributes with dynamic names. If - true, the tag-class must implement the - javax.servlet.jsp.tagext.DynamicAttributes - interface. Defaults to false. - - example Optional informal description of an - example of a use of this tag - - tag-extension Zero or more extensions that provide extra - information about this tag, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="name" - type="j2ee:tld-canonical-nameType"/> - <xsd:element name="tag-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines the subclass of javax.serlvet.jsp.tagext.JspTag - that implements the request time semantics for - this tag. (required) - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tei-class" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines the subclass of javax.servlet.jsp.tagext.TagExtraInfo - for this tag. (optional) - - If this is not given, the class is not consulted at - translation time. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="body-content" - type="j2ee:body-contentType"> - <xsd:annotation> - <xsd:documentation> - - Specifies the format for the body of this tag. - The default in JSP 1.2 was "JSP" but because this - is an invalid setting for simple tag handlers, there - is no longer a default in JSP 2.0. A reasonable - default for simple tag handlers is "scriptless" if - the tag can have a body. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="variable" - type="j2ee:variableType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="attribute" - type="j2ee:tld-attributeType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="dynamic-attributes" - type="j2ee:generic-booleanType" - minOccurs="0"/> - <xsd:element name="example" - type="j2ee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of a tag. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tag-extension" - type="j2ee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Tag extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-attributeType"> - <xsd:annotation> - <xsd:documentation> - - The attribute element defines an attribute for the nesting - tag. The attributre element may have several subelements - defining: - - description a description of the attribute - - name the name of the attribute - - required whether the attribute is required or - optional - - rtexprvalue whether the attribute is a runtime attribute - - type the type of the attributes - - fragment whether this attribute is a fragment - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="name" - type="j2ee:java-identifierType"/> - <xsd:element name="required" - type="j2ee:generic-booleanType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines if the nesting attribute is required or - optional. - - If not present then the default is "false", i.e - the attribute is optional. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:choice> - <xsd:sequence> - <xsd:element name="rtexprvalue" - type="j2ee:generic-booleanType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines if the nesting attribute can have scriptlet - expressions as a value, i.e the value of the - attribute may be dynamically calculated at request - time, as opposed to a static value determined at - translation time. - - If not present then the default is "false", i.e the - attribute has a static value - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="type" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines the Java type of the attributes value. For - static values (those determined at translation time) - the type is always java.lang.String. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:element name="fragment" - type="j2ee:generic-booleanType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - "true" if this attribute is of type - javax.jsp.tagext.JspFragment, representing dynamic - content that can be re-evaluated as many times - as needed by the tag handler. If omitted or "false", - the default is still type="java.lang.String" - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-canonical-nameType"> - - <xsd:annotation> - <xsd:documentation> - - Defines the canonical name of a tag or attribute being - defined. - - The name must conform to the lexical rules for an NMTOKEN. - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="j2ee:xsdNMTOKENType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-extensionType"> - <xsd:annotation> - <xsd:documentation> - - The tld-extensionType is used to indicate - extensions to a specific TLD element. - - It is used by elements to designate an extension block - that is targeted to a specific extension designated by - a set of extension elements that are declared by a - namespace. The namespace identifies the extension to - the tool that processes the extension. - - The type of the extension-element is abstract. Therefore, - a concrete type must be specified by the TLD using - xsi:type attribute for each extension-element. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="extension-element" - type="j2ee:extensibleType" - maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="namespace" - use="required" - type="xsd:anyURI"/> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tldTaglibType"> - <xsd:annotation> - <xsd:documentation> - - The taglib tag is the document root, it defines: - - description a simple string describing the "use" of this taglib, - should be user discernable - - display-name the display-name element contains a - short name that is intended to be displayed - by tools - - icon optional icon that can be used by tools - - tlib-version the version of the tag library implementation - - short-name a simple default short name that could be - used by a JSP authoring tool to create - names with a mnemonic value; for example, - the it may be used as the prefered prefix - value in taglib directives - - uri a uri uniquely identifying this taglib - - validator optional TagLibraryValidator information - - listener optional event listener specification - - tag tags in this tag library - - tag-file tag files in this tag library - - function zero or more EL functions defined in this - tag library - - taglib-extension zero or more extensions that provide extra - information about this taglib, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="j2ee:descriptionGroup"/> - <xsd:element name="tlib-version" - type="j2ee:dewey-versionType"> - <xsd:annotation> - <xsd:documentation> - - Describes this version (number) of the taglibrary. - It is described as a dewey decimal. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - <xsd:element name="short-name" - type="j2ee:tld-canonical-nameType"> - <xsd:annotation> - <xsd:documentation> - - Defines a simple default name that could be used by - a JSP authoring tool to create names with a - mnemonicvalue; for example, it may be used as the - preferred prefix value in taglib directives. Do - not use white space, and do not start with digits - or underscore. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="uri" - type="j2ee:xsdAnyURIType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines a public URI that uniquely identifies this - version of the taglibrary. Leave it empty if it - does not apply. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="validator" - type="j2ee:validatorType" - minOccurs="0"> - </xsd:element> - <xsd:element name="listener" - type="j2ee:listenerType" - minOccurs="0" maxOccurs="unbounded"> - </xsd:element> - <xsd:element name="tag" - type="j2ee:tagType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="tag-file" - type="j2ee:tagFileType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="function" - type="j2ee:functionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="taglib-extension" - type="j2ee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Taglib extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="version" - type="j2ee:dewey-versionType" - fixed="2.0" - use="required"> - <xsd:annotation> - <xsd:documentation> - - Describes the JSP version (number) this taglibrary - requires in order to function (dewey decimal) - - </xsd:documentation> - </xsd:annotation> - - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="validatorType"> - <xsd:annotation> - <xsd:documentation> - - A validator that can be used to validate - the conformance of a JSP page to using this tag library is - defined by a validatorType. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="validator-class" - type="j2ee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines the TagLibraryValidator class that can be used - to validate the conformance of a JSP page to using this - tag library. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="j2ee:param-valueType" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The init-param element contains a name/value pair as an - initialization param. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="variable-scopeType"> - <xsd:annotation> - <xsd:documentation> - - This type defines scope of the scripting variable. See - TagExtraInfo for details. The allowed values are, - "NESTED", "AT_BEGIN" and "AT_END". - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="j2ee:string"> - <xsd:enumeration value="NESTED"/> - <xsd:enumeration value="AT_BEGIN"/> - <xsd:enumeration value="AT_END"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="variableType"> - <xsd:annotation> - <xsd:documentation> - - The variableType provides information on the scripting - variables defined by using this tag. It is a (translation - time) error for a tag that has one or more variable - subelements to have a TagExtraInfo class that returns a - non-null value from a call to getVariableInfo(). - - The subelements of variableType are of the form: - - description Optional description of this - variable - - name-given The variable name as a constant - - name-from-attribute The name of an attribute whose - (translation time) value will - give the name of the - variable. One of name-given or - name-from-attribute is required. - - variable-class Name of the class of the variable. - java.lang.String is default. - - declare Whether the variable is declared - or not. True is the default. - - scope The scope of the scripting varaible - defined. NESTED is default. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="j2ee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="name-given" - type="j2ee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The name for the scripting variable. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="name-from-attribute" - type="j2ee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The name of an attribute whose - (translation-time) value will give the name of - the variable. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - <xsd:element name="variable-class" - type="j2ee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The optional name of the class for the scripting - variable. The default is java.lang.String. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - <xsd:element name="declare" - type="j2ee:generic-booleanType" - minOccurs="0"> - - <xsd:annotation> - <xsd:documentation> - - Whether the scripting variable is to be defined - or not. See TagExtraInfo for details. This - element is optional and "true" is the default. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="scope" - type="j2ee:variable-scopeType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The element is optional and "NESTED" is the default. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - diff --git a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_1.xsd b/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_1.xsd deleted file mode 100644 index bea8e9b1c9..0000000000 --- a/bundles/org.eclipse.jst.standard.schemas/dtdsAndSchemas/web-jsptaglibrary_2_1.xsd +++ /dev/null @@ -1,1144 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<xsd:schema - 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="2.1"> - - <xsd:annotation> - <xsd:documentation> - @(#)web-jsptaglibrary_2_1.xsds 1.1 - </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 JSP Taglibrary - descriptor. All Taglibrary descriptors must - indicate the tag library schema by using the Taglibrary - namespace: - - http://java.sun.com/xml/ns/javaee - - and by indicating the version of the schema by - using the version element as shown below: - - <taglib xmlns="http://java.sun.com/xml/ns/javaee" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="..." - version="2.1"> - ... - </taglib> - - The instance documents may indicate the published - version of the schema using xsi:schemaLocation attribute - for Java EE namespace with the following location: - - http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd - - ]]> - </xsd:documentation> - </xsd:annotation> - - <xsd:include schemaLocation="javaee_5.xsd"/> - - -<!-- **************************************************** --> - - <xsd:element name="taglib" type="javaee:tldTaglibType"> - <xsd:annotation> - <xsd:documentation> - - The taglib tag is the document root. - The definition of taglib is provided - by the tldTaglibType. - - </xsd:documentation> - </xsd:annotation> - <xsd:unique name="tag-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The taglib element contains, among other things, tag and - tag-file elements. - The name subelements of these elements must each be unique. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:tag|javaee:tag-file"/> - <xsd:field xpath="javaee:name"/> - </xsd:unique> - - <xsd:unique name="function-name-uniqueness"> - <xsd:annotation> - <xsd:documentation> - - The taglib element contains function elements. - The name subelements of these elements must each be unique. - - </xsd:documentation> - </xsd:annotation> - <xsd:selector xpath="javaee:function"/> - <xsd:field xpath="javaee:name"/> - </xsd:unique> - - </xsd:element> - - -<!-- **************************************************** --> - - <xsd:complexType name="body-contentType"> - <xsd:annotation> - <xsd:documentation> - - Specifies the type of body that is valid for a tag. - This value is used by the JSP container to validate - that a tag invocation has the correct body syntax and - by page composition tools to assist the page author - in providing a valid tag body. - - There are currently four values specified: - - tagdependent The body of the tag is interpreted by the tag - implementation itself, and is most likely - in a different "language", e.g embedded SQL - statements. - - JSP The body of the tag contains nested JSP - syntax. - - empty The body must be empty - - scriptless The body accepts only template text, EL - Expressions, and JSP action elements. No - scripting elements are allowed. - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="tagdependent"/> - <xsd:enumeration value="JSP"/> - <xsd:enumeration value="empty"/> - <xsd:enumeration value="scriptless"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="extensibleType" abstract="true"> - <xsd:annotation> - <xsd:documentation> - - The extensibleType is an abstract base type that is used to - define the type of extension-elements. Instance documents - must substitute a known type to define the extension by - using xsi:type attribute to define the actual type of - extension-elements. - - </xsd:documentation> - </xsd:annotation> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="functionType"> - <xsd:annotation> - <xsd:documentation> - - The function element is used to provide information on each - function in the tag library that is to be exposed to the EL. - - The function element may have several subelements defining: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name A unique name for this function - - function-class Provides the name of the Java class that - implements the function - - function-signature Provides the signature, as in the Java - Language Specification, of the Java - method that is to be used to implement - the function. - - example Optional informal description of an - example of a use of this function - - function-extension Zero or more extensions that provide extra - information about this function, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="name" - type="javaee:tld-canonical-nameType"> - <xsd:annotation> - <xsd:documentation> - - A unique name for this function. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="function-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Provides the fully-qualified class name of the Java - class containing the static method that implements - the function. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="function-signature" - type="javaee:string"> - <xsd:annotation> - <xsd:documentation> - - Provides the signature, of the static Java method that is - to be used to implement the function. The syntax of the - function-signature element is as follows: - - FunctionSignature ::= ReturnType S MethodName S? - '(' S? Parameters? S? ')' - - ReturnType ::= Type - - MethodName ::= Identifier - - Parameters ::= Parameter - | ( Parameter S? ',' S? Parameters ) - - Parameter ::= Type - - Where: - - * Type is a basic type or a fully qualified - Java class name (including package name), - as per the 'Type' production in the Java - Language Specification, Second Edition, - Chapter 18. - - * Identifier is a Java identifier, as per - the 'Identifier' production in the Java - Language Specification, Second - Edition, Chapter 18. - - Example: - - java.lang.String nickName( java.lang.String, int ) - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="example" - type="javaee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of this function. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="function-extension" - type="javaee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Function extensions are for tool use only and must not - affect the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tagFileType"> - <xsd:annotation> - <xsd:documentation> - - Defines an action in this tag library that is implemented - as a .tag file. - - The tag-file element has two required subelements: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name The unique action name - - path Where to find the .tag file implementing this - action, relative to the root of the web - application or the root of the JAR file for a - tag library packaged in a JAR. This must - begin with /WEB-INF/tags if the .tag file - resides in the WAR, or /META-INF/tags if the - .tag file resides in a JAR. - - example Optional informal description of an - example of a use of this tag - - tag-extension Zero or more extensions that provide extra - information about this tag, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="name" - type="javaee:tld-canonical-nameType"/> - <xsd:element name="path" - type="javaee:pathType"/> - <xsd:element name="example" - type="javaee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of a tag. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tag-extension" - type="javaee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Tag extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tagType"> - <xsd:annotation> - <xsd:documentation> - - The tag defines a unique tag in this tag library. It has one - attribute, id. - - The tag element may have several subelements defining: - - description Optional tag-specific information - - display-name A short name that is intended to be - displayed by tools - - icon Optional icon element that can be used - by tools - - name The unique action name - - tag-class The tag handler class implementing - javax.servlet.jsp.tagext.JspTag - - tei-class An optional subclass of - javax.servlet.jsp.tagext.TagExtraInfo - - body-content The body content type - - variable Optional scripting variable information - - attribute All attributes of this action that are - evaluated prior to invocation. - - dynamic-attributes Whether this tag supports additional - attributes with dynamic names. If - true, the tag-class must implement the - javax.servlet.jsp.tagext.DynamicAttributes - interface. Defaults to false. - - example Optional informal description of an - example of a use of this tag - - tag-extension Zero or more extensions that provide extra - information about this tag, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="name" - type="javaee:tld-canonical-nameType"/> - <xsd:element name="tag-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines the subclass of javax.serlvet.jsp.tagext.JspTag - that implements the request time semantics for - this tag. (required) - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tei-class" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines the subclass of javax.servlet.jsp.tagext.TagExtraInfo - for this tag. (optional) - - If this is not given, the class is not consulted at - translation time. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="body-content" - type="javaee:body-contentType"> - <xsd:annotation> - <xsd:documentation> - - Specifies the format for the body of this tag. - The default in JSP 1.2 was "JSP" but because this - is an invalid setting for simple tag handlers, there - is no longer a default in JSP 2.0. A reasonable - default for simple tag handlers is "scriptless" if - the tag can have a body. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="variable" - type="javaee:variableType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="attribute" - type="javaee:tld-attributeType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="dynamic-attributes" - type="javaee:generic-booleanType" - minOccurs="0"/> - <xsd:element name="example" - type="javaee:xsdStringType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The example element contains an informal description - of an example of the use of a tag. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="tag-extension" - type="javaee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Tag extensions are for tool use only and must not affect - the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-attributeType"> - <xsd:annotation> - <xsd:documentation> - - The attribute element defines an attribute for the nesting - tag. The attribute element may have several subelements - defining: - - description a description of the attribute - - name the name of the attribute - - required whether the attribute is required or - optional - - rtexprvalue whether the attribute is a runtime attribute - - type the type of the attributes - - fragment whether this attribute is a fragment - - deferred-value present if this attribute is to be parsed as a - javax.el.ValueExpression - - deferred-method present if this attribute is to be parsed as a - javax.el.MethodExpression - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:element name="name" - type="javaee:java-identifierType"/> - <xsd:element name="required" - type="javaee:generic-booleanType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines if the nesting attribute is required or - optional. - - If not present then the default is "false", i.e - the attribute is optional. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:choice> - <xsd:sequence> - <xsd:sequence minOccurs="0"> - <xsd:element name="rtexprvalue" - type="javaee:generic-booleanType"> - <xsd:annotation> - <xsd:documentation> - - Defines if the nesting attribute can have scriptlet - expressions as a value, i.e the value of the - attribute may be dynamically calculated at request - time, as opposed to a static value determined at - translation time. - If not present then the default is "false", i.e the - attribute has a static value - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="type" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines the Java type of the attributes value. - If this element is omitted, the expected type is - assumed to be "java.lang.Object". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - - <xsd:choice> - <xsd:element name="deferred-value" - type="javaee:tld-deferred-valueType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Present if the value for this attribute is to be - passed to the tag handler as a - javax.el.ValueExpression. This allows for deferred - evaluation of EL expressions. An optional subelement - will contain the expected type that the value will - be coerced to after evaluation of the expression. - The type defaults to Object if one is not provided. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="deferred-method" - type="javaee:tld-deferred-methodType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Present if the value for this attribute is to be - passed to the tag handler as a - javax.el.MethodExpression. This allows for deferred - evaluation of an EL expression that identifies a - method to be invoked on an Object. An optional - subelement will contain the expected method - signature. The signature defaults to "void method()" - if one is not provided. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - </xsd:sequence> - - <xsd:element name="fragment" - type="javaee:generic-booleanType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - "true" if this attribute is of type - javax.jsp.tagext.JspFragment, representing dynamic - content that can be re-evaluated as many times - as needed by the tag handler. If omitted or "false", - the default is still type="java.lang.String" - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - </xsd:choice> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-canonical-nameType"> - - <xsd:annotation> - <xsd:documentation> - - Defines the canonical name of a tag or attribute being - defined. - - The name must conform to the lexical rules for an NMTOKEN. - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="javaee:xsdNMTOKENType"/> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-deferred-methodType"> - <xsd:annotation> - <xsd:documentation> - - Defines information about how to provide the value for a - tag handler attribute that accepts a javax.el.MethodExpression. - - The deferred-method element has one optional subelement: - - method-signature Provides the signature, as in the Java - Language Specifies, that is expected for - the method being identified by the - expression. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="method-signature" - type="javaee:string" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Provides the expected signature of the method identified - by the javax.el.MethodExpression. - - This disambiguates overloaded methods and ensures that - the return value is of the expected type. - - The syntax of the method-signature element is identical - to that of the function-signature element. See the - documentation for function-signature for more details. - - The name of the method is for documentation purposes only - and is ignored by the JSP container. - - Example: - - boolean validate(java.lang.String) - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-deferred-valueType"> - <xsd:annotation> - <xsd:documentation> - - Defines information about how to provide the value for a - tag handler attribute that accepts a javax.el.ValueExpression. - - The deferred-value element has one optional subelement: - - type the expected type of the attribute - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="type" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The fully-qualified name of the Java type that is the - expected type for this deferred expression. If this - element is omitted, the expected type is assumed to be - "java.lang.Object". - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tld-extensionType"> - <xsd:annotation> - <xsd:documentation> - - The tld-extensionType is used to indicate - extensions to a specific TLD element. - - It is used by elements to designate an extension block - that is targeted to a specific extension designated by - a set of extension elements that are declared by a - namespace. The namespace identifies the extension to - the tool that processes the extension. - - The type of the extension-element is abstract. Therefore, - a concrete type must be specified by the TLD using - xsi:type attribute for each extension-element. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="extension-element" - type="javaee:extensibleType" - maxOccurs="unbounded"/> - </xsd:sequence> - - <xsd:attribute name="namespace" - use="required" - type="xsd:anyURI"/> - <xsd:attribute name="id" type="xsd:ID"/> - - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="tldTaglibType"> - <xsd:annotation> - <xsd:documentation> - - The taglib tag is the document root, it defines: - - description a simple string describing the "use" of this - taglib, should be user discernable - - display-name the display-name element contains a - short name that is intended to be displayed - by tools - - icon optional icon that can be used by tools - - tlib-version the version of the tag library implementation - - short-name a simple default short name that could be - used by a JSP authoring tool to create - names with a mnemonic value; for example, - the it may be used as the prefered prefix - value in taglib directives - - uri a uri uniquely identifying this taglib - - validator optional TagLibraryValidator information - - listener optional event listener specification - - tag tags in this tag library - - tag-file tag files in this tag library - - function zero or more EL functions defined in this - tag library - - taglib-extension zero or more extensions that provide extra - information about this taglib, for tool - consumption - - </xsd:documentation> - </xsd:annotation> - <xsd:sequence> - <xsd:group ref="javaee:descriptionGroup"/> - <xsd:element name="tlib-version" - type="javaee:dewey-versionType"> - <xsd:annotation> - <xsd:documentation> - - Describes this version (number) of the taglibrary. - It is described as a dewey decimal. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - <xsd:element name="short-name" - type="javaee:tld-canonical-nameType"> - <xsd:annotation> - <xsd:documentation> - - Defines a simple default name that could be used by - a JSP authoring tool to create names with a - mnemonicvalue; for example, it may be used as the - preferred prefix value in taglib directives. Do - not use white space, and do not start with digits - or underscore. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="uri" - type="javaee:xsdAnyURIType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - Defines a public URI that uniquely identifies this - version of the taglibrary. Leave it empty if it - does not apply. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - <xsd:element name="validator" - type="javaee:validatorType" - minOccurs="0"> - </xsd:element> - <xsd:element name="listener" - type="javaee:listenerType" - minOccurs="0" maxOccurs="unbounded"> - </xsd:element> - <xsd:element name="tag" - type="javaee:tagType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="tag-file" - type="javaee:tagFileType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="function" - type="javaee:functionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="taglib-extension" - type="javaee:tld-extensionType" - minOccurs="0" - maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - Taglib extensions are for tool use only and must not - affect the behavior of a container. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="version" - type="javaee:dewey-versionType" - fixed="2.1" - use="required"> - <xsd:annotation> - <xsd:documentation> - - Describes the JSP version (number) this taglibrary - requires in order to function (dewey decimal) - - </xsd:documentation> - </xsd:annotation> - - </xsd:attribute> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="validatorType"> - <xsd:annotation> - <xsd:documentation> - - A validator that can be used to validate - the conformance of a JSP page to using this tag library is - defined by a validatorType. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" - maxOccurs="unbounded"/> - <xsd:element name="validator-class" - type="javaee:fully-qualified-classType"> - <xsd:annotation> - <xsd:documentation> - - Defines the TagLibraryValidator class that can be used - to validate the conformance of a JSP page to using this - tag library. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="init-param" - type="javaee:param-valueType" - minOccurs="0" maxOccurs="unbounded"> - <xsd:annotation> - <xsd:documentation> - - The init-param element contains a name/value pair as an - initialization param. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="variable-scopeType"> - <xsd:annotation> - <xsd:documentation> - - This type defines scope of the scripting variable. See - TagExtraInfo for details. The allowed values are, - "NESTED", "AT_BEGIN" and "AT_END". - - </xsd:documentation> - </xsd:annotation> - - <xsd:simpleContent> - <xsd:restriction base="javaee:string"> - <xsd:enumeration value="NESTED"/> - <xsd:enumeration value="AT_BEGIN"/> - <xsd:enumeration value="AT_END"/> - </xsd:restriction> - </xsd:simpleContent> - </xsd:complexType> - -<!-- **************************************************** --> - - <xsd:complexType name="variableType"> - <xsd:annotation> - <xsd:documentation> - - The variableType provides information on the scripting - variables defined by using this tag. It is a (translation - time) error for a tag that has one or more variable - subelements to have a TagExtraInfo class that returns a - non-null value from a call to getVariableInfo(). - - The subelements of variableType are of the form: - - description Optional description of this - variable - - name-given The variable name as a constant - - name-from-attribute The name of an attribute whose - (translation time) value will - give the name of the - variable. One of name-given or - name-from-attribute is required. - - variable-class Name of the class of the variable. - java.lang.String is default. - - declare Whether the variable is declared - or not. True is the default. - - scope The scope of the scripting varaible - defined. NESTED is default. - - </xsd:documentation> - </xsd:annotation> - - <xsd:sequence> - <xsd:element name="description" - type="javaee:descriptionType" - minOccurs="0" maxOccurs="unbounded"/> - <xsd:choice> - <xsd:element name="name-given" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The name for the scripting variable. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - - <xsd:element name="name-from-attribute" - type="javaee:java-identifierType"> - <xsd:annotation> - <xsd:documentation> - - The name of an attribute whose - (translation-time) value will give the name of - the variable. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:choice> - <xsd:element name="variable-class" - type="javaee:fully-qualified-classType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The optional name of the class for the scripting - variable. The default is java.lang.String. - - </xsd:documentation> - </xsd:annotation> - - </xsd:element> - - <xsd:element name="declare" - type="javaee:generic-booleanType" - minOccurs="0"> - - <xsd:annotation> - <xsd:documentation> - - Whether the scripting variable is to be defined - or not. See TagExtraInfo for details. This - element is optional and "true" is the default. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - <xsd:element name="scope" - type="javaee:variable-scopeType" - minOccurs="0"> - <xsd:annotation> - <xsd:documentation> - - The element is optional and "NESTED" is the default. - - </xsd:documentation> - </xsd:annotation> - </xsd:element> - </xsd:sequence> - <xsd:attribute name="id" type="xsd:ID"/> - </xsd:complexType> - -</xsd:schema> - |