Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Deployment Exceptions (14001 - 14033)

`DeploymentException` is a run-time exception that is raised if problems are detected during deployment of an EJB bean. During deployment, project, sessions, and `ejb-jar.xml` files (or their Java Class equivalents) are read, and the necessary objects are instantiated and initialized.

Format

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

Example 13-15 Deployment Exception

    EXCEPTION [TOPLINK – 14001]: oracle.toplink.ejb.DeploymentException
    EXCEPTION DESCRIPTION: No TopLink project was specified for this bean.

14001: NO_PROJECT_SPECIFIED
  Cause: Neither project name nor class could be read from the deployment descriptor.
  Action: Verify your project configuration in your deployment descriptor. Double- check that either `project-xml` or `project-class` is specified.

14003: NO_SUCH_PROJECT_IDENTIFIER
  Cause: No project exists with the identifier requested.
  Action: Verify that the project name matches exactly the project name specified in your project XML file.

14004: ERROR_CREATING_CUSTOMIZATION
  Cause: Could not create an instance of the `DeploymentCustomization` class.
  Action: Verify the implementation of the class implementing the `DeploymentCustomization` interface. Start with the constructor, then proceed to the remainder of the implementation.

14005: ERROR_RUNNING_CUSTOMIZATION
  Cause: An exception was raised when either the `afterLoginCustomization` method or the `beforeLoginCustomization` method of the DeploymentCustomization was called.
  Action: See the generated exception for the root cause. Verify the implementation of your `DeploymentCustomization` method.

14011: ERROR_CONNECTING_TO_DATA_SOURCE
  Cause: The data source could not be located in JNDI, or was not properly specified.
  Action: Verify the data source attribute of the login element in your `sessions.xml` file. Ensure that the data source is present and properly configured.

14016: ERROR_CREATING_PROJECT
  Cause: The project XML file name or class was specified, but a general error occurred creating the project.
  Action: See the generated exception for the root cause. Verify your `project.xml` file.

14020: ERROR_IN_DEPLOYMENT_DESCRIPTOR
  Cause: Error parsing the `toplink-ejb-jar.xml` file.
  Action: See the generated exception for the root cause. Verify your `toplink-ejb-jar.xml` file.

14023: CANNOT_FIND_GENERATED_SUBCLASS
  Cause: An internal, unexpected exception was raised.
  Action: See the exception message provided.

14024: CANNOT_READ_TOPLINK_PROJECT
  Cause: An internal, unexpected exception was raised while reading the project.
  Action: See the exception message provided.

14026: MUST_USE_TRANSPARENT_INDIRECTION
  Cause: Your project contains either a one-to-many or many-to-many relationship (between EJB 2.0 entity beans) that is not using transparent indirection.
  Action: Verify your project is using transparent indirection for all one-to-many and many-to-many relationships involving EJB 2.0 entity beans.

14027: MUST_USE_VALUEHOLDER
  Cause: Your project contains a one-to-one relationship (between EJB 2.0 entity beans) that is not using basic indirection.
  Action: Verify your project is using basic indirection for all one-to-one relationships involving EJB 2.0 entity beans.

14028: NO_SUCH_MAPPING
  Cause: The specified descriptor does not contain a corresponding mapping for the specified container managed attribute.
  Action: Verify the descriptor and ensure that you configure a mapping for the specified container managed attribute.

14029: MISSING_FINDER_DEF
  Cause: The specified finder is declared in the `ejb-jar.xml` file but not defined on the specified home interface.
  Action: Verify the specified home interface and ensure that you define the specified finder in it.

14030: MISSING_EJB_SELECT_DEF
  Cause: The specified `ejbSelect` method is declared in the `ejb-jar.xml` file but not defined on the specified abstract bean class.
  Action: Verify the specified abstract bean class and ensure that you define the specified `ejbSelect` method on it.

14031: MISSING_11_CMP_FIELD
  Cause: The specified EJB 1.1 CMP field is declared in the `ejb-jar.xml` file but not defined on the specified bean.
  Action: Verify the specified bean class and ensure that you define the specified CMP field in it.

14032: MISSING_20_CMP_FIELD
  Cause: The specified EJB 2.0 CMP field is declared in the `ejb-jar.xml` file but the corresponding abstract getter and/or setter is not defined on the specified abstract bean class.
  Action: Verify the specified abstract bean class and ensure that you define the specified abstract getter and/or setter on it.

14033: MISSING_DESCRIPTOR
  Cause: The descriptor for the specified class is missing.
  Action: Verify your TopLink project.xml and ensure that you create and configure a descriptor for the specified class.