Description
The EJB specifications do not require CMP 2.x containers to enforce foreign key constraints. Such a capability seems to be a quality of implementation, that OpenEJB will support.
An element needs to be added to the OpenEJB DD in order to turn on such a capability. When activated, the flush strategy used under the cover of the transactional cache re-arranges the SQL operations to avoid foreign key constraint conflicts.