Cause: The class not found is not included on the WebSphere application extensions classpath or in the EJB or WAR module.
Action: Ensure that all required classes are included in the correct location.
Refer to the "Setting classpaths" information in the IBM WebSphere InfoCenter for detailed information on classpath locations.
Cause: The required TopLink JARs have not been copied into the application extensions classpath.
Action: Ensure that toplink.jar, tl_wasx.jar, antlr.jar are copied into the <WebSphere install>\lib\app directory. For running the examples, hsqldb.jar and hsql_ds.jar must also be copied into the <WebSphere install>\lib\app directory.
oracle.toplink.exceptions.DatabaseException
Cause: A TopLink Exception has occurred.
Action: Refer to "Runtime and Development Exceptions" on page 1-1 and look up the error code that is observed (the error code should be displayed in square brackets, such as [TopLink-1016]). Errors observed here may be errors in reading in the properties file, or validation errors due to improper mappings.
Exception [6066]
oracle.toplink.exceptions.QueryException: The object <Object>
of class <class> with identity hashcode <hashcode> is not from this unit of work object space but the parent session’s. The object was never registered in this unit of work, but read from the parent session and related to an object registered in the unit of work. Ensure that you are correctly registering your objects. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() method to help debug where the error occurred. Please see the manual and FAQ for more information.
Cause: A bean was created outside of a transaction and then a second was created either in or out of a transaction.
Action: Ensure that all creates are done with in the context of a transaction.
Cause: The bean was not cleared out during ejbPassivate.
Action: Ensure that the ejbPassivate clears out the bean.
Cause: A bean-to-object relationships is not privately owned.
Action: Ensure that bean-to-object relationships are privately owned.
Exception [7064]
oracle.toplink.exceptions.ValidationException: Exception occured in reflective EJB bean primary key extraction, please ensure your primary key object is defined correctly:
key = 301, bean = <beanName>
Cause: An incorrect primary key object is being used with a bean.
Action: Ensure that you are using the correct primary key object for a bean.
Exception [7066]
oracle.toplink.exceptions.ValidationException: Cannot create or remove beans unless a JTS transaction is present, bean=<bean>
Cause: An attempt was made to create or remove a been outside of a transaction.
Action: Ensure that all removing and creating of beans is done within a transaction.
Exception [7068]
oracle.toplink.exceptions.ValidationException: The project class <projectclass> was not found for the <toplink_
session_name> using default class loader.
Cause: The project class specified in the TOPLink.properties file for the session specified on the toplink_session_name environment variable can not be found.
Action: Check that the project class given in the exception is on the WebSphere dependent classpath.
Exception [7069]
oracle.toplink.exceptions.ValidationException: An exception occured looking up or invoking the project amendment method, <amendmentMethod> on the class <amendmentClass>;
Cause: An amendment method was called but can not be found.
Action: Check that the required amendment method exists on the class specified.
Exception [7070]
oracle.toplink.exceptions.ValidationException: A
TOPLink.properties resource bundle must be located on the classpath in a TOPLink directory.
Cause: The TOPLink.properties file can not be found.
Action: Make sure that the location of the TOPLink.properties files is on the classpath. If the exception is within VisualAge the TOPLink.properties file must be in the project resources for the TopLink project.
Exception [7079]
EXCEPTION DESCRIPTION: The descriptor for [<bean class>] was not found in the session [<session name>]. Check the project being used for this session.
Cause: The descriptor listed was not found in the session specified on the deployment descriptor.
Action: Check that the project specified in the toplink-ejb-jar.xml file is the desired project. Also check that the project includes a descriptor for the missing bean class.
Exception [7101]
No "meta-inf/toplink-ejb-jar.xml" could be found in your classpath. The CMP session could not be read in from file.
Cause: The toplink-ejb-jar.xml file was not found.
Action: Make sure that the toplink-ejb-jar.xml file is located in the deployed ejb jar file under the meta-inf directory.
Exception [9002]
EXCEPTION [TOPLINK-9002] (TopLink - X.X.X):
oracle.toplink.exceptions.SessionLoaderExceptionEXCEPTION DESCRIPTION: Unable to load Project class [<project class>].
Cause: The project class specified for the session in the toplink-ejb-jar.xml file cannot be found.
Action: Check that the project class has been included in the deployed jar with the entity beans.
Problems Occurring at Runtime Using TopLink for WebSphere Foundation Library
This section lists some of the common exceptions and errors that can occur at runtime when using the TopLink CMP for IBM WebSphere Application Server.
Exception [6026]
oracle.toplink.exceptions: Query is not defined Cause: A required named query does not exist.
Action: Implement the named query. The stacktrace of the exception will contain the finder that failed.