Skip Headers

# EJB JAR XML Exceptions (72000 – 72023)

Previous

Next

`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

EJB JAR XML Exception

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

72000: READ_EXCEPTION
  Cause: Failure 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: Failure 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.

72002: CONCRETE_INSTANCE_VARIALBE_EXISTS
  Cause: There was a concrete instance variable `variableName` already defined on the class `ClassName`.
  Action: Either remove this instance variable from the class, refresh in the TopLink Workbench, and update from the `ejb-jar.xml` file again, or remove the field from the `ejb-jar.xml` file and update again.

72003: EJB_2_0_ATTRIBUTE_NOT_EXIST
  Cause: A mapping for a field `fieldName` could not be created on the descriptor `DescriptorName`.
  Action: Check to ensure that there are abstract `get` and `set` methods accessible for this field.

72004: NEITHER_HOME_NOR_REMOTE_INTERFACE_FOUND
  Cause: Neither local home nor remote home interface for the class ClassName was found on the classpath. The finders for this class were not updated
  Action: Update the finders for this class; ensure that either local home or remote home interface for the class is on the classpath.

72005: FINDER_NOT_EXIST_ON_REMOTE_HOME_AND_LOCAL_HOME
  Cause: The finder method methodName was not defined on a home interface for the entity `EntityName`. The finder was not updated
  Action: Define the finder method.

72006: NO_PERSISTENCE_TYPE_SPECIFIED
  Cause: TopLink Workbench could not determine a project persistence type from the XML file.
  Action: Specify the persistence type for your TopLink project.

72007: SELECT_NOT_DEFINED_IN_BEANCLASS
  Cause: Failure to find a corresponding `ejbSelect` method in the bean class `ClassName`. No information was updated for this query.
  Action: Define `ejbSelect` method in your bean class.

72008: EJB_DESCRIPTOR_MUST_HAVE_EJB_NAME
  Cause: The EJB descriptor `DescriptorName` does not have an EJB name specified.
  Action: In your EJB descriptor, specify an EJB name.

72009: EJB_DESCRIPTOR_MUST_HAVE_PRIMARYKEY_CLASS
  Cause: The EJB descriptor `DescriptorName` does not have a primary key class specified.
  Action: In your EJB descriptor, specify a primary key class.

72010: EJB_NAME_MUST_BE_UNIQUE
  Cause: The EJB name `EJBName` was used by more than one descriptor. EJB names must be unique
  Action: Ensure that the EJB name is specified in one and only one descriptor.

72011: EMPTY_TEXT_ATTRIBUTE
  Cause: An element `elementName` has an empty text attribute `attributeName`.
  Action: Use a non-empty text attribute for the subelement.

72012: MULTIPLE_ENTITIES_FOUND_FOR_EJB_NAME
  Cause: There are multiple entities with the same EJB bean name `BeanName` in the XML file.
  Action: Use a unique EJB bean name for each entity.

72013: INVALID_CMP_VERSION
  Cause: The entity EntityName does not have a valid `cmp-version` definition. 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 BeanName in the `ejb-relationship-role` element 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 `Mapping` Name in a descriptor `DescriptorName`. The multiplicity must be either `One` or `Many`.
  Action: Use a multiplicity value of `One` or `Many` only.

72016: INVALID_PERSISTENCE_TYPE
  Cause: The entity EntityName does not have a valid persistence type. The type must be either `Bean` or `Container`.
  Action: Use a `persistence-type` value of `Bean` or `Container` only.

72017: INVALID_QUERY_METHOD_NAME
  Cause: The query method `methodName` does not start with `find` or `ejbSelect`. No information was updated for this query.
  Action: Verify that the query method name starts with either `find` or `ejbSelect`.

72018: NOT_SINGLE_PERSISTENCE_TYPE
  Cause: Attempt to use a nonuniform persistence type for the TopLink Workbench project: 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: Provide all entities in the XML file for this project with the same `persistence-type` and/or `cmp-version`.

72019: PROJECT_MUST_HAVE_AT_LEAST_ONE_EJB_DESCRIPTOR
  Cause: The project `ProjectName` does not have an EJB descriptor: it must have at least one EJB descriptor.
  Action: Provide an EJB descriptor for the project.

72020: ATTRIBUTE_NOT_EXIST
  Cause: The attribute `attributeName` is not found.
  Action: Define this attribute.

72021: EJB_CLASS_NOT_FOUND
  Cause: The class `ClassName` could not be found on the classpath. A descriptor could not be created for it.
  Action: Ensure that the class ClassName is on the classpath.

72022: REQUIRED_ATTRIBUTE_NOT_EXIST
  Cause: There is an element that does not have a required attribute.
  Action: Add the subelement to the parent element.

72023: NO_CMR_FIELD_FOR_BEAN_ABSTRACT_SETTER
  Cause: Entity bean BeanName has an abstract setter method with an `EntityBean` attribute type for attribute `attributeName`, but does not have a corresponding CMR field.
  Action: Verify that all CMP entities have the same `cmp-version` value.