Here are two scenarios that this problem might occur:
The converter defined for the primary key is not invoked on its foreign key value.
- During ejbDeploy, you may receive the following message: "No type mapping defined for Java_data_type1 to database_data_type2"
- During execution time, the application may not be able to find the CMP at the other end of the relationship.
A workaround to this limitation is to define your own foreign key and use the same converter defined for its primary key on the EJB at the other end of its relationship.
Editing the activation-config properties of an annotated EJB 2.1 message-driven bean from the Activity Configuration section of the EJB deployment descriptor editor has some problems and puts the bean in an unstable state. Do not use the Activity Configuration section of the editor for any edits to the activation-config properties, but rather use the Source page of the editor.
The EJB tooling only supports the generation of session bean facades for EJB 2.x CMP entity beans in projects that are targeted to WebSphere Application Server V6. You can change the target server in the project properties.
In the EJB JAR Import wizard there is an option to create a new EJB project. If you create a new EJB project during import and select "Create an EJB Client JAR Project to hold the client interfaces and classes", an error results and the new project creation does not work properly.
Return to the main readme file