Sunday, January 2, 2005 04:41 PM
On enabling cascade delete for any Entity Bean paticipating in CMR, it causes all related bean instances to be deleted by the container if the current bean is deleted.
This way you do not get FK violation exceptions even if the underlying database does not support ON DELETE CASCADE
Please check how does the vendor of the app server you are using implements Cascade delete. PLEASE NOTE THE multiplicity
In ejb-jar.xml this is how you enable