The DD not conforming to EJB-JAR DTD (ejb-jar_1_1.dtd, ejb-jar_2_0.dtd, ejb-jar_2_1.xsd, ejb-jar_3.0.xsd and ejb-jar_3.1.xsd) becomes an error when importing EJB-JAR because the required items are not specified or the specification order is invalid, and therefore, you cannot import EJB-JAR. When you cannot import EJB-JAR, revise ejb-jar.xml settings.

With the Entity Bean CMP, you cannot specify CMP field names and CMR field names beginning with underscore (_).

Do not use double-byte codes with EJB QL.

In the role-link included in the <security-role-ref> tag, specify the role name specified in the role-name included in the <security-role> tag.

With the <method-name> tag included in the<query-method> tag of the ejb-jar.xml, you cannot code * (asterisk). You cannot import EJB-JAR containing ejb-jar.xml with * (asterisk) specified in the <query-method> tag.

The <abstract-schema-name> tag cannot be duplicated with the name specified in other <abstract-schema-name> tags that exist in the same file and with the names specified in cmp-field, cmr-field. Also, you cannot use the reserved words of EJB QL in the <abstract-schema-name> tag.

The <display-name> tag included in the <ejb-jar> tag is used as the file name in the work directory. Specify the <display-name> tag such that the path length of the work directory does not reach the upper limit for the OS (the default is specified on the basis of the EJB-JAR file name). For details on estimating the path length of the work directory, see Appendix C.1 Work directory of J2EE server in the manual uCosminexus Application Server System Setup and Operation Guide.

With Developer, the functions of the <ejb-client-jar> tag of a DD coded in ejb-jar.xml are not supported.

When you set a <relationships> tag with ejb-jar.xml, specify the <cmr-field> tag in any one of two <ejb-relationship-role> tags.

You cannot code Processing Instruction, XInclusion, and a name space prefix in the DD of each project. Even if a value is coded, the value is not read correctly.