EJB tools - release notes


1.0 Limitations
   1.1 Converters defined on primary key does not get invoked on the foreign key
2.0 Known problems
   2.1 *Error while creating new EJB project through the EJB JAR Import wizard

1.0 Limitations

1.1 Converters defined on primary key does not get invoked on the foreign key

Here are two scenarios that this problem might occur:

  1. During ejbDeploy, you may receive the following message: "No type mapping defined for Java_data_type1 to database_data_type2"
  2. During execution time, the application may not be able to find the CMP at the other end of the relationship.
The converter defined for the primary key is not invoked on its foreign key value.

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.

2.0 Known problems

2.1 *Error while creating new EJB project through the EJB JAR Import wizard

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.

Note: This has been fixed in V6.0.0.1.

Return to the main readme file