EJB JAR XML Exceptions (72000 – 72022)

EJBJARXMLException is a run-time exception that is raised at deployment time when the ejb-jar.xml file is read and the required concrete EJB classes code is generated.

Format

EXCEPTION [TOPLINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Example 13-27 EJB JAR XML Exception

EXCEPTION [TOPLINK – 72000]: oracle.toplink.exceptions.EJBJarXMLException
EXCEPTION DESCRIPTION: Error reading ejb-jar.xml file.

72000: READ_EXCEPTION

Cause: Failed to read an ejb-jar.xml file due to a java.io.IOException or javax.xml.parsers.ParserConfigurationException.

Action: See the generated exception for the root cause.

72001: INVALID_DOC_TYPE

Cause: Failed to parse the specified file because it did not use the expected doctype: -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN

Action: Verify that your ejb-jar.xml file uses the correct documentation type.

72003: EJB_2_0_ATTRIBUTE_NOT_EXIST

Cause: A mapping for a field could not be created on the descriptor.

Action: Check to ensure that there are abstract get and set methods accessible for this field.

72011: EMPTY_TEXT_ATTRIBUTE

Cause: The element cannot have an empty text attribute.

Action: Use a non-empty text attribute for the sub-element.

72012: MULTIPLE_ENTITIES_FOUND_FOR_EJB_NAME

Cause: There are multiple entities with the same EJB bean name in the XML file.

Action: Use a unique EJB bean name for each entity.

72013: INVALID_CMP_VERSION

Cause: The entity did not have a valid cmp-version. The cmp-version must be 1.x or 2.x.

Action: Use a cmp-version value of 1.x or 2.x only.

72014: INVALID_EJB_NAME_FOR_RELATIONSHIP_ROLE

Cause: The EJB bean name in the ejb-relationship-role is not found in the XML file.

Action: Use the EJB bean name of an existing entity for the ejb-relationship-role.

72015: INVALID_MULTIPLICITY

Cause: There was an invalid multiplicity value defined for a relationship involving the mapping in a descriptor. The multiplicity must be One or Many.

Action: Use a multiplicity value of One or Many only.

72016: INVALID_PERSISTENCE_TYPE

Cause: The entity did not have a valid persistence type. The type must be Bean or Container.

Action: Use a persistence-type value of Bean or Container only.

72017: INVALID_QUERY_METHOD_NAME

Cause: The query method-name does not start with find or ejbSelect. No information was updated for this query.

Action: Verify that the method-name value starts with find or ejbSelect.

72018: NOT_SINGLE_PERSISTENCE_TYPE

Cause: TopLink Workbench requires that all entities in the XML file for this project have the same persistence-type and/or cmp-version. The project will be set according to the persistence-type and/or cmp-version of the first entity in the file.

Action: Verify that all CMP entities have the same cmp-version value.

72022: REQUIRED_ATTRIBUTE_NOT_EXIST

Cause: There is an element that does not have a required attribute.

Action: Add the sub-element to the parent element.