Skip Headers

# EJB QL Exceptions (8001 – 8010)

Previous

Next

`EJBQLException` is a run-time exception that is raised when the EJB QL string does not parse properly, or the contents cannot be resolved within the context of the TopLink session. The associated message typically includes a reference to the EJB QL string that caused the problem.

Format

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

EJB QL Exception

    EXCEPTION [TOPLINK – 8002]: oracle.toplink.exceptions.EJBQLException
    EXCEPTION DESCRIPTION: TopLink has encountered a problem while parsing the EJB QL string.

8001: recognitionException
  Cause: The TopLink EJB QL parser does not recognize a clause in the EJB QL string.
  Action: Validate the EJB QL string.

8002: generalParsingException
  Cause: TopLink has encountered a problem while parsing the EJB QL string.
  Action: Check the internal exception for details on the root cause of this exception.

8003: classNotFoundException
  Cause: The class specified in the EJB QL string was not found.
  Action: Ensure that the class is on the appropriate classpath.

8004: aliasResolutionException
  Cause: TopLink was unable to resolve the alias used in the EJB QL string.
  Action: Validate the identifiers used in the EJB QL string.

8005: resolutionClassNotFoundException
  Cause: TopLink was unable to resolve the class for an alias. This means that the class specified cannot be found.
  Action: Ensure that the class is specified properly and is on the classpath.

8006: missingDescriptorException
  Cause: The class specified in the query does not have a TopLink descriptor.
  Action: Ensure that the class has been mapped and is specified correctly in the EJB QL string.

8009: expressionNotSupported
  Cause: An unsupported expression was used in the EJB QL.
  Action: Change the query to use only supported expressions.

8010: generalParsingException2
  Cause: TopLink has encountered a problem while parsing the EJB QL string.
  Action: Check the internal exception for details on the root cause of this exception.