[Ejtools-cvs] build/dtd application-client_1_2.dtd,NONE,1.1 application-client_1_3.dtd,NONE,1.1 appl
Brought to you by:
letiemble
Menu
▾
▴
[Ejtools-cvs] build/dtd application-client_1_2.dtd,NONE,1.1 application-client_1_3.dtd,NONE,1.1 application_1_2.dtd,NONE,1.1 application_1_3.dtd,NONE,1.1 connector_1_0.dtd,NONE,1.1 ejb-jar_1_1.dtd,NONE,1.1 ejb-jar_2_0.dtd,NONE,1.1 struts-config_1_0.dtd,NONE,1.1 web-app_2_2.dtd,NONE,1.1 web-app_2_3.dtd,NONE,1.1 web-jsptaglibrary_1_1.dtd,NONE,1.1 web-jsptaglibrary_1_2.dtd,NONE,1.1
|
From: <let...@us...> - 2002-06-10 07:45:33
|
Update of /cvsroot/ejtools/build/dtd In directory usw-pr-cvs1:/tmp/cvs-serv12939/dtd Added Files: application-client_1_2.dtd application-client_1_3.dtd application_1_2.dtd application_1_3.dtd connector_1_0.dtd ejb-jar_1_1.dtd ejb-jar_2_0.dtd struts-config_1_0.dtd web-app_2_2.dtd web-app_2_3.dtd web-jsptaglibrary_1_1.dtd web-jsptaglibrary_1_2.dtd Log Message: Switch to Ant 1.5 beta 2 --- NEW FILE: application-client_1_2.dtd --- <!-- 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> --- NEW FILE: application-client_1_3.dtd --- <!-- 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> --- NEW FILE: application_1_2.dtd --- <!-- 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> --- NEW FILE: application_1_3.dtd --- <!-- 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> --- NEW FILE: connector_1_0.dtd --- <!-- 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 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 d... [truncated message content] |
