📄 j2ee_1_4.xsd
字号:
</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>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -