<ejb-jar>
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.
<description>A short description</description>
A short description.
<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.
<small-icon>employee-service-icon16x16.jpg</small-icon>
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.
<large-icon>employee-service-icon32x32.jpg</large-icon>
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.
<enterprise-beans>
The enterprise-beans element contains the declarations of one or more enterprise beans.
<session>
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 factory references. The elements that are optional are "optional" in the sense that they are omitted when if lists represented by them are empty.
<description>A short description</description>
A short description.
<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.
<small-icon>employee-service-icon16x16.jpg</small-icon>
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.
<large-icon>employee-service-icon32x32.jpg</large-icon>
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.
<ejb-name>EmployeeService</ejb-name>
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.
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
The ejb-class element contains the fully-qualified name of the enterprise bean's class.
<session-type>Stateful/Stateless</session-type>
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: Stateful or Stateless.
<transaction-type>Bean/Container</transaction-type>
The transaction-type element must be one of the two following: Bean or Container.
<transaction-scope>Local|Distributed</transaction-scope>
The transaction-scope element specifies whether an enterprise bean requires that distributed transactions must be used for its methods of whether the local transaction optimization may be used. The transaction-scope element must be one of the two following: Local Distributed The transaction-scope element is optional. If it is not specified, the container must assume that distributed transactions must be used.
<env-entry>
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.
<description>A short description</description>
A short description.
<env-entry-name>minAmount</env-entry-name>
The env-entry-name element contains the name of an enterprise bean's environment entry.
<env-entry-type>java.lang.String</env-entry-type>
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.
<env-entry-value>100.00</env-entry-value>
The env-entry-value element contains the value of an enterprise bean's environment entry.
<ejb-ref>
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.
<description>A short description</description>
A short description.
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
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/".
<ejb-ref-type>Entity|Session</ejb-ref-type>
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: Entity Session
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-link>EmployeeRecord</ejb-link>
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.
<security-role-ref>
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.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<role-link>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.
<security-identity>
The security-identity element specifies whether the caller's security identity is to be used for the execution of the methods of the enter-prise bean or whether a specific run-as identity is to be used.
<description>A short description</description>
A short description.
<use-caller-identity>myRole</use-caller-identity>
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.
<run-as-specified-identity>
The run-as-specified-identity element specifies the run-as identity to be used for the execution of the methods of an enterprise bean.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<resource-ref>
The resource-ref element contains a declaration of enterprise bean'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 enterprise bean code, and the type of authentication (bean or container).
<description>A short description</description>
A short description.
<res-ref-name>name</res-ref-name>
The res-ref-name element specifies the name of a resource factory reference.
<res-type>javax.sql.DataSource</res-type>
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.
<res-auth>Application/Container</res-auth>
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: Application or Container
<resource-env-ref>
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 indica-tion of the resource environment reference type expected by the enter-prise bean code. Used in: entity, message-driven and session Examples: jms/StockQueue javax.jms.Queue
<description>A short description</description>
A short description.
<resource-env-ref-name>theName</resource-env-ref-name>
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.
<resource-env-ref-type>com.the.Type</resource-env-ref-type>
The resource-env-ref-type element specifies the type of a resource environment reference.
<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 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.
<description>A short description</description>
A short description.
<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.
<small-icon>employee-service-icon16x16.jpg</small-icon>
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.
<large-icon>employee-service-icon32x32.jpg</large-icon>
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.
<ejb-name>EmployeeService</ejb-name>
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.
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
The ejb-class element contains the fully-qualified name of the enterprise bean's class.
<persistence-type>Bean|Container</persistence-type>
The persistence-type element specifies an entity bean's persistence management type. The persistence-type element must be one of the two following: Bean or Container.
<prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
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.
<reentrant>True/False</reentrant>
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
<cmp-version>1.x|2.x</cmp-version>
The cmp-version element specifies the version of an entity bean with container-managed persistence. The following are the legal values of the cmp-version element: 1.x and 2.x. The default value of the cmp-version element is 2.x.
<abstract-schema-name>OrderBean</abstract-schema-name>
The abstract-schema-name element specifies the name of the abstract schema 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 might be OrderBean if its entity bean class is com.acme.commerce.OrderBean.
<cmp-field>
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.
<description>A short description</description>
A short description.
<field-name>firstName</field-name>
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.
<primkey-field>fieldName</primkey-field>
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.
<transaction-scope>Local|Distributed</transaction-scope>
The transaction-scope element specifies whether an enterprise bean requires that distributed transactions must be used for its methods of whether the local transaction optimization may be used. The transaction-scope element must be one of the two following: Local Distributed The transaction-scope element is optional. If it is not specified, the container must assume that distributed transactions must be used.
<env-entry>
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.
<description>A short description</description>
A short description.
<env-entry-name>minAmount</env-entry-name>
The env-entry-name element contains the name of an enterprise bean's environment entry.
<env-entry-type>java.lang.String</env-entry-type>
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.
<env-entry-value>100.00</env-entry-value>
The env-entry-value element contains the value of an enterprise bean's environment entry.
<ejb-ref>
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.
<description>A short description</description>
A short description.
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
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/".
<ejb-ref-type>Entity|Session</ejb-ref-type>
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: Entity Session
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-link>EmployeeRecord</ejb-link>
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.
<security-role-ref>
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.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<role-link>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.
<security-identity>
The security-identity element specifies whether the caller's security identity is to be used for the execution of the methods of the enter-prise bean or whether a specific run-as identity is to be used.
<description>A short description</description>
A short description.
<use-caller-identity>myRole</use-caller-identity>
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.
<run-as-specified-identity>
The run-as-specified-identity element specifies the run-as identity to be used for the execution of the methods of an enterprise bean.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<resource-ref>
The resource-ref element contains a declaration of enterprise bean'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 enterprise bean code, and the type of authentication (bean or container).
<description>A short description</description>
A short description.
<res-ref-name>name</res-ref-name>
The res-ref-name element specifies the name of a resource factory reference.
<res-type>javax.sql.DataSource</res-type>
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.
<res-auth>Application/Container</res-auth>
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: Application or Container
<resource-env-ref>
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 indica-tion of the resource environment reference type expected by the enter-prise bean code. Used in: entity, message-driven and session Examples: jms/StockQueue javax.jms.Queue
<description>A short description</description>
A short description.
<resource-env-ref-name>theName</resource-env-ref-name>
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.
<resource-env-ref-type>com.the.Type</resource-env-ref-type>
The resource-env-ref-type element specifies the type of a resource environment reference.
<query>
The query element is used to specify a finder or select query. It con-tains an optional description of the query, the specification of the finder or select method it is used by, and the EJB QL query string or query specification that defines the query.
<description>A short description</description>
A short description.
<query-method>
The query-method element is used to specify the method for finder or a 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 within the method-params element. Used in: query Example: Method finds large orders ejbFindLargeOrders WHERE amount > 1000
<method-name>nameOfMethod</method-name>
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.
<method-params>
The method-params element contains a list of the fully-qualified Java type names of the method parameters.
<method-param>int[]</method-param>
The method-param element contains the fully-qualified Java type name of a method parameter.
<ejb-ql>QUERY</ejb-ql>
The ejb-ql element contains the EJB QL finder or select 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. If ejb-ql element is not specified, the query-spec element must be used to specify the semantics of the query. Used in: query Example: ejbSelectPendingLineitemsInEntity SELECT l FROM l in lineitems WHERE shipped is FALSE
<query-spec>SPEC</query-spec>
The query-spec element is used to specify a finder or select query. It contains a precise description of the semantics of the query. The query-spec element should only be used to specify queries whose seman- tics cannot be captured in EJB QL.
<message-driven>
The message-driven element declares a message-driven 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 mes-sage- driven bean's implementation class; the message-driven bean's transaction management type; an optional declaration as to whether distributed or local transactions should be used for the bean's onMes-sage method; 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 message-driven bean's intended destination type; an optional declaration of the bean's environment entries; an optional declaration of the bean's EJB refer-ences; 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 factory references; and an optional declaration of the bean's resource environment references.
<description>A short description</description>
A short description.
<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.
<small-icon>employee-service-icon16x16.jpg</small-icon>
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.
<large-icon>employee-service-icon32x32.jpg</large-icon>
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.
<ejb-name>EmployeeService</ejb-name>
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.
<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
The ejb-class element contains the fully-qualified name of the enterprise bean's class.
<transaction-type>Bean/Container</transaction-type>
The transaction-type element must be one of the two following: Bean or Container.
<transaction-scope>Local|Distributed</transaction-scope>
The transaction-scope element specifies whether an enterprise bean requires that distributed transactions must be used for its methods of whether the local transaction optimization may be used. The transaction-scope element must be one of the two following: Local Distributed The transaction-scope element is optional. If it is not specified, the container must assume that distributed transactions must be used.
<jms-message-selector>JMSType = 'car'</jms-message-selector>
The jms-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.
<jms-acknowledge-mode>AUTO_ACKNOWLEDGE|DUPS_OK_ACKNOWLEDGE</jms-acknowledge-mode>
The jms-acknowledge-mode element specifies whether JMS AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE message acknowledgment seman- tics should be used for the onMessage message of a message-driven bean that uses bean managed transaction demarcation. The jms-acknowledge-mode element must be one of the two following: auto-acknowledge dups-ok-acknowledge
<message-driven-destination>
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 mes-sage- driven bean's intended destination and an optional declaration of whether a durable or non-durable subscription should be used if the message-driven bean is assigned to a Topic.
<jms-destination-type>javax.jms.Queue|javax.jms.Topic</jms-destination-type>
The jms-destination-type element specifies the type of the JMS desti-nation. The type is specified by the Java interface expected to be implemented by the destination. The jms-destination-type element must be one of the two following: javax.jms.Queue javax.jms.Topic
<jms-subscription-durability>durable|nondurable</jms-subscription-durability>
The jms-subscription-durability element specifies whether a JMS topic subscription is intended to be durable or nondurable. The jms-subscription-durability element must be one of the two following: durable nondurable
<env-entry>
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.
<description>A short description</description>
A short description.
<env-entry-name>minAmount</env-entry-name>
The env-entry-name element contains the name of an enterprise bean's environment entry.
<env-entry-type>java.lang.String</env-entry-type>
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.
<env-entry-value>100.00</env-entry-value>
The env-entry-value element contains the value of an enterprise bean's environment entry.
<ejb-ref>
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.
<description>A short description</description>
A short description.
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
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/".
<ejb-ref-type>Entity|Session</ejb-ref-type>
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: Entity Session
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-link>EmployeeRecord</ejb-link>
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.
<security-identity>
The security-identity element specifies whether the caller's security identity is to be used for the execution of the methods of the enter-prise bean or whether a specific run-as identity is to be used.
<description>A short description</description>
A short description.
<use-caller-identity>myRole</use-caller-identity>
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.
<run-as-specified-identity>
The run-as-specified-identity element specifies the run-as identity to be used for the execution of the methods of an enterprise bean.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<resource-ref>
The resource-ref element contains a declaration of enterprise bean'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 enterprise bean code, and the type of authentication (bean or container).
<description>A short description</description>
A short description.
<res-ref-name>name</res-ref-name>
The res-ref-name element specifies the name of a resource factory reference.
<res-type>javax.sql.DataSource</res-type>
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.
<res-auth>Application/Container</res-auth>
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: Application or Container
<resource-env-ref>
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 indica-tion of the resource environment reference type expected by the enter-prise bean code. Used in: entity, message-driven and session Examples: jms/StockQueue javax.jms.Queue
<description>A short description</description>
A short description.
<resource-env-ref-name>theName</resource-env-ref-name>
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.
<resource-env-ref-type>com.the.Type</resource-env-ref-type>
The resource-env-ref-type element specifies the type of a resource environment reference.
<dependents>
The dependents element contains the declaration of one or more dependent object classes that are used (directly or indirectly) in relationships with entity beans with container managed persistence.
<description>A short description</description>
A short description.
<dependent>
The dependent element specifies a dependent object class of an entity bean with container managed persistence. The element consists of the dependent object's class; the unique name that is used for the dependent object class; and the fields that are persisted by the container on its behalf. Example: com.acme.Address Address street city zip country
<description>A short description</description>
A short description.
<dependent-class>TheDependentClass</dependent-class>
The dependent-class element contains the fully qualified name of the dependent object class.
<dependent-name>dependentName</dependent-name>
The dependent-name element specifies a name that uniquely designates a dependent object class.
<cmp-field>
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.
<description>A short description</description>
A short description.
<field-name>firstName</field-name>
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.
<relationships>
The relationships element describes the relationships that the con-tainer managed persistence entity beans and dependent objects partic-ipate in. This element must declare the references to entity beans and dependent classes that participate in container managed relationships by means of the ejb-entity-ref and dependent-ref elements, and spec-ify the container managed relationships in the ejb-relation elements.
<description>A short description</description>
A short description.
<ejb-entity-ref>
Like the ejb-ref element, the ejb-entity-ref element is used for declaring a reference to an enterprise bean's home and remote. How-ever, this element also contains the remote-ejb-name element, which provides a name for the remote entity bean. This name is used within relationships and EJB QL queries to refer to the entity bean specified by the ejb-entity-ref element. The ejb-ref-name element is provided to allow the container to locate the bean by using JNDI. Used in: relationships Example: This is a reference descriptor for an order bean which is used in product.jar OrderEJB ejb/Order com.commercewarehouse.catalog.OrderHome com.commercewarehouse.catalog.Order ../orders/orders.jar#OrderEJB
<description>A short description</description>
A short description.
<remote-ejb-name>nameOfRemoteEJB</remote-ejb-name>
The remote-ejb-name elements specifies the name of an entity bean which is not provided in the ejb-jar file. The name is used to designate a role in a relationship and declared by the ejb-entity-ref element.
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
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/".
<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.
<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.
<ejb-link>EmployeeRecord</ejb-link>
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.
<ejb-relation>
The ejb-relation element describes a relationship between two entity-beans, between an entity bean and a dependent object class, or between two dependent object classes of an entity bean. An ejb-relation element contains exactly two role declarations, defined by the ejb-relationship-role elements. The name of the relationship is unique within the ejb-jar file and defined by the ejb-relation-name element.
<description>A short description</description>
A short description.
<ejb-relation-name>ejbRelationName</ejb-relation-name>
The ejb-relation-name element provides a name for a relationship.
<ejb-relationship-role>
The ejb-relationship-role element describes a role within a relation-ship. There are two roles in each relationship. The role-name, multiplicity and role-source are mandatory. The role-source element designates an entity-bean or dependent object class by means of an ejb-name, remote-ejb-name or dependent-name ele-ment. For bidirectional relationships, both roles of a relationship must declare a role-source element that specifies the 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 entity bean or the dependent class that participates in the relationship is "not aware" of the relationship and the relationship is unidirectional. Used in: ejb-relation Example: Product-LineItem product-has-lineitems one ProductEJB
<description>A short description</description>
A short description.
<ejb-relationship-role-name>ejbRelationshipRoleName</ejb-relationship-role-name>
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.
<multiplicity>one|many</multiplicity>
The multiplicity element describes the multiplicity of the role that participates in a relation. The multiplicity element must be one of the two following: one or many.
<role-source>
The role-source element designates the source of a role that participates in a relationship. A role-source element contains a reference which uniquely identifies an entity bean or dependent object class. The Bean Provider must ensure that the content of each role-source element refers to an existing entity bean, entity bean reference, or dependent object class.
<description>A short description</description>
A short description.
<ejb-name>EmployeeService</ejb-name>
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.
<remote-ejb-name>nameOfRemoteEJB</remote-ejb-name>
The remote-ejb-name elements specifies the name of an entity bean which is not provided in the ejb-jar file. The name is used to designate a role in a relationship and declared by the ejb-entity-ref element.
<dependent-name>dependentName</dependent-name>
The dependent-name element specifies a name that uniquely designates a dependent object class.
<cmr-field>
The cmr-field element describes the bean provider's view of a relationship. It consists of the name and the class type of a field in the source of a role of a relationship. The name of the field corresponds to the name used for the get and set accessor methods for the relationship. The cmr-field-type element must only be used to specify the type of collection for a one-to-many or many-to-many relationship.
<description>A short description</description>
A short description.
<cmr-field-name>nameOfField</cmr-field-name>
The cmr-field-name element specifies the name of a relationship field in the entity bean or the dependent object class. This field is accessed by methods whose names consists of the name of the field specified by cmr-field-name prefixed by "get" or "set".
<cmr-field-type>java.util.Collection|java.util.Set</cmr-field-type>
The cmr-field-type element specifies the class of a collection-valued relationship field in the entity bean or dependent class. The value of the cmr-field-type element must be either: java.util.Collection or java.util.Set.
<assembly-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.
<security-role>
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.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<method-permission>
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.
<description>A short description</description>
A short description.
<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.
<method>
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[][]).
<description>A short description</description>
A short description.
<ejb-name>EmployeeService</ejb-name>
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.
<method-intf>Home/Remote</method-intf>
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: Home or Remote.
<method-name>nameOfMethod</method-name>
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.
<method-params>
The method-params element contains a list of the fully-qualified Java type names of the method parameters.
<method-param>int[]</method-param>
The method-param element contains the fully-qualified Java type name of a method parameter.
<container-transaction>
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.
<description>A short description</description>
A short description.
<method>
<description>A short description</description>
A short description.
<ejb-name>EmployeeService</ejb-name>
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.
<method-intf>Home/Remote</method-intf>
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: Home or Remote.
<method-name>nameOfMethod</method-name>
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.
<method-params>
The method-params element contains a list of the fully-qualified Java type names of the method parameters.
<method-param>int[]</method-param>
The method-param element contains the fully-qualified Java type name of a method parameter.
<trans-attribute>Supports</trans-attribute>
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: NotSupported, Supports, Required, RequiresNew, Mandatory or Never
<ejb-client-jar>employee_service_client.jar</ejb-client-jar>
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.
本文地址：http://com.8s8s.com/it/it11685.htm