Limitations of EJB development tools

This topic outlines current known limitations and restrictions for the EJB tooling.

EJB query language (EJB QL) limitations and restrictions

EJB mapping limitations and restrictions

Deleting tables and schemas

If a table needs to be deleted, use the Data perspective or the Project Explorer view of the J2EE perspective, then all dependent links will also be removed. Normally you should not use the Navigator view (in the Resource perspective) or the J2EE Project Navigator view for deleting J2EE resources because dependencies will not be updated.

Unknown primary key is not supported

The EJB tooling currently does not support the Unknown primary key definition described in the EJB 2.0 specification. The workaround is to define a specific primary key class.

Source page and EJB inheritance

If you are modifying CMP entity beans in an inheritance hierarchy, you should use the wizards and interface portions of the EJB deployment descriptor editor, not the Source page. For example, if you want to add or remove CMP fields or change the primary key field of a CMP bean, these fields are synchronized by the tools for all inherited beans, in order to keep the beans in compliance with the EJB specification. Such synchronization may not occur if you change the source in the Source page.

Linux icon (Linux™) Connection problems when running a 1.1 CMP bean against DB2 on a WebSphere Application Server V4 (Unit Test Environment)

You might encounter connection problems when you run a 1.1 CMP bean against DB2 in the Unit Test Environment of WebSphere Application Server V4.
Workaround: Set loopback for your database. For example, if your database is named MyDB, your hostname is LHOST, and your database service port number is 50000, issue the following commands:
db2 catalog TCPIP node RHOST remote LHOST server 50000
db2 catalog database MyDB as MyDBAlias
db2 uncatalog db MyDB
db2 catalog database MyDBAlias as MyDB at node RHOST
To verify whether this works, issue the following command, where xxx is your password:
db2 connect to MyDB user xxx

Arabic characters not supported for Java™ files and enterprise beans

Do not use Arabic characters in names for Java files, enterprise beans, or access beans. Do not use Arabic characters when working through the MiniBank example.

Migrating EJB applications

Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.